We are using:
• NServiceBus 7.1.6
• NServiceBus.SqlServer 4.1
In an effort to clean up data for an old, non-existent endpoint, I foolishly deleted some queues (tables) manually without removing their subscriptions from the publisher. We’ve now gotten everything cleaned up, so no real harm except to my ego.
That said, I want to better understand the behavior that occurred when we saw these in the logs:
NServiceBus.RecoverabilityExecutor Immediate Retry is going to retry message ‘xxxxxxxxxxxxxxxxxxxxxxxxxx’ because of an exception:
NServiceBus.Unicast.Queuing.QueueNotFoundException: Failed to send message to [QUEUENAME] —> System.Data.SqlClient.SqlException: Invalid object name ‘[QUEUENAME]’.
This was a published event, with multiple subscribers–only one of the queues was missing. Would the “valid” subscribers have received the message multiple times? In other words, would the retry attempt to republish the message again to all subscribers, or just to the subscriber whose queue was invalid?