Closed sfmskywalker closed 3 years ago
I just realized that I should probably have filed this issue under the Rebus Azure Service Bus project. Let me know if I should re-create it there.
Ah, so I just came across rebus-org/Rebus#60 and rebus-org/Rebus#61, and tried Rebus.AzureServiceBus 8.0.0-a1
, which seems to work a little bit better in that it now no longer throws the exception I mentioned. However, something still doesn't seem right, because only "endpoint3" is now receiving the "This one should be received by all! => 'endpoint3'"
message. Console output:
This one should be received by all! => 'endpoint3'
Press ENTER to quit
Sounds weird with the InvalidOperationException
... but, could I get you to remove the wildcards from the subscribers' topics?
Azure Service Bus doesn't support wildcards in topics like RabbitMQ does, so a topic like mercedes.#
doesn't "catch" events published to any of the used topics. I would expect Rebus to "sanitize" the topic though, so it probably subscribes without an error to a topic like mercedes__
, or something like that. But it obviously won't receive anything in this particular sample.
Ah, good thinking! Indeed that change made things work again 😁
Thanks!
In order to see how to use the Azure Service Bus provider works, I cloned the Rebus Samples repository and updated the RabbitTopics project to use the Azure Service Bus provider. Before the change, the program worked as advertised. But when I run the program with my changes, it fails with the following error:
Here's my complete Program.cs file:
I also updated the .csproj file as follows in order to make things build on my local machine:
I made sure that I didn't break things by making sure the RabbitMQ provider still works.