We are publishing message to a Topic (multicast) that has a subscriber that is conditional - therefore, it will only purposely pickup certain messages. The issue is that for messages that do not meet the condition criteria there is no subscriber and a SubscriberNotFound exception is logged along with putting the message in the Failure table.
We've created a dummy subscriber to handle these other messages with a dummy business process with a single Cancel step, but also needed to bind it with a dummy endpoint so it will run. So a lot of dummy stubs.
Only other alternative I see is to be put conditions within the Publish business process to not publish to the bus, but seems to me to defeat the purpose of having conditional subscribers (plus it's a lot cleaner for us to have the conditions on the subscriber than in a publisher bus process - especially since in the future we may create subscribers for the other conditions)
Is there a better suggestion to do this?
the topic (tcp or named pipe) has a property "Log no recipient" set by default to true "Log a warning when there are no recipients for a message"
I think this could make the trick, I don't think we are currently using it, but I remember playing with it, you should try if it works
That did indeed suppress the "Warning" of no eligible subscriber, but unfortunately the "Error" is still reported, with the message logged into the Failed Messages table.