CODEWITHSUNDEEP
c#rebus
dampee
dampee

Reputation: 3437

What happens to Rebus failed messages

In older versions of Rebus you could control the error queue. But now you only have a "inputQueue" in the azure servicebus extender. How can I control the error queue?

Bus = Configure.With(_adapter)
            .Transport(t => t.UseAzureServiceBus(ConnectionString, inputQueue /*, errorQueue */))
            .Start();

UPDATE: they end up in the "error" queue. I have now messages from different sources in the same (error)queue. So, the question became, can rebus filter out messages where the input queue matches the custom property rbs2-source-queue?

Upvotes: 2

Views: 1527

Answers (1)

mookid8000
mookid8000

Reputation: 18628

The error queue is still configurable!

You made me realize that this was not something that I had mentioned on the wiki though, so I just went and added it :)

The solution to configuring which error queue to use is pretty simple - check this out:

Configure.With(...)
    .Options(b => b.SimpleRetryStrategy(errorQueueAddress: "somewhere_else"))
    .(...)

As you have correctly discovered, the rbs2-source-queue header reveals which input queue the message failed too many times in, and therefore it can be used for filtering the failed messages later on. There's no way, though, to only receive those messages that have a specific value in that header.

Upvotes: 2

Related Questions