Hi all,
I'm expirimenting with some pub/sub events in serveral applications. I would like to prevent error messages for messages that have no subscribers (sometimes an event just has no listeners for it because we use several document versions of the event in parallel and subscribers take only one of the versions for example). In my publishing orchestration I already have a catch for the 'PersistanceException' but I still get a nice 'his service instance exists to help debug routing failures for instance... bla bla bla'-non resumable-message in my message box.
In some blog (http://blog.codit.eu/post/2009/12/09/Suppress-routing-failure-reports-in-BizTalk-Server-2009.aspx) I found a promissing article for the BTS.SuppressRoutingFailureDiagnosticInfo property which sounds like exactly what I need. So I wrote the property to the context (value true) and promoted it using a correlationset when I publish the message to the message box.... Still got the routing failure report.
I also did some expiriments using the BTS.SuspendAsNonResumable (set to false) andBTS.SuspendMessageOnRoutingFailure (also set to false) but nothing has the desired result
Am I missing something or is this a bug in BizTalk (I'm using 2010 and this was a late addition to 2006 so I think that's very unlikely)? Is there prehaps an other way to prevent the routing failure reports?
Regards, Ferdinand.