Rebus | :bus: Simple and lean service bus implementation for NET | Messaging library

Hello all (and most probably @mookid8000),

I am using Rebus C# library with Azure Storage queue. Everything works fine, just have one issue with logging.

Rebus is making several GetMessage calls to queue per second. That is extremely problematic, because it generates GB of data per day if "queue" operations are being logged to Log Analytics, which cost a lot money.

Is there a way to tell rebus to check the queue only each 10s, or each minute if last response return no new messages? My app doesn't need fast message handling, so slower refresh period between each call to queue is preferable anyway.

Maybe it can be configured somewhere here?

I have a Rebus bus setup with a single worker and max parallelism of 1 that processes messages "sequentialy". In case an handler fails, or for specific business reason, I'd like the bus instance to immediately stop processing messages.

I tried using the Rebus.Event package to detect the exception in the AfterMessageHandled handler and set the number of workers to 0, but it seems other messages are processed before it can actually succeed in stoping the single worker instance.

Where in the event processing pipeline could I do bus.Advanced.Workers.SetNumberOfWorkers(0); in order to prevent further message processing?

I also tried setting the number of workers to 0 inside a catch block in the handler itself, but it doesn't seem like the right place to do it since SetNumberOfWorkers(0) waits for handlers to complete before returning and the caller is the handler... Looks like a some kind of a deadlock to me.

Thank you

I am in the process of writing some unit tests for my Rebus Handlers. I have opted to enable secondLevelRetriesEnabled which results in an IFailed being published when an exception is thrown in the Handler.

My Handler class definition is:

We have a .net core 3.1 web project running with Rebus and Azure Service Bus.

After updating to .NET 5 we can no longer send messages to the Azure Service Bus queue using Rebus. No code changes have been made, only update to .NET 5 and latest Rebus-packages(6.6.1).

*Edit: Thanks to Martin and a little bit of time and attention, I was able to get the code where I needed it to be. Is it ugly? Yes, but it works in way that's useful to me now. Any tips on how to clean this up and make it more efficient would be super helpful.

Using the data frame trace_list, I'm trying to append the values from Title and Year to the output of each list in the for loop. The following code opens each state's PDF link on page 10, pulls the city data (which ranges from 1-12 cities). Clean/tidies the data, and stores it in a list to be bound after data from each PDF is collected. Right now it only pulls the city name and a numerical value.

I have strings from which I need to extract all matches from a vector using the rebus package.

I am trying to publish a message from the catch block in the Rebus message handlers without affecting the retry mechanism of rebus.

My intent is,

• Process the message in message handlers.
• In case of an error, catch it, and publish some error event using the same bus.
• Just after publishing "throw" the caught exception so that rebus ACK/NACK is placed automatically for the retry/re-delivery of the message.

I cannot achieve the above because if an exception is thrown from the rebus message handlers, that message is automatically flagged for re-delivery and the whole pipeline transaction is rolled back. This negates the second point above as when transaction is rolled back, the message I sent to be published is rolled back as well. Is there a way I could achieve this i.e. publishing the message as well as auto-retry ability. My message handler code is below.

I have a class that I use as a message type in Rebus to publish/subscribe to, but I hit a snag when I was trying out a proof-of-concept in LinqPad. Any messages that my app receives fails with a deserialization exception. I have been able to narrow down the issue to Newtonsoft.JSON package and come up with the minimal example to demonstrate the issue:

I know, that rebus stores errors across message deliveries in IErrorTraker (InMemErrorTracker). Is there any way to inject IErrorTraker to handlers or another way to get exception from previous attempt? Thanks!