Closed mathiasnohall closed 3 years ago
Sounds like Rebus.RabbitMq needs to have its RabbitMq.Client dependency updated.
OK, work is ongoing in making Rebus.RabbitMq work with version 6.1 of the driver.
Many of the tests are passing now, but some of them experience weird errors that indicates having received some kind of mangled message body.
Gonna park it for now – most recent code is on master.
Gonna park it for now
any news on updating the client driver version?
oh, it's been a long time since I've looked at it.... I'll see if I can get back to this in the coming week
waiting。。。
Bumping this.
https://github.com/rebus-org/Rebus.RabbitMq/pull/71
solves this. I have tested it in our code enviroment and it works. Some unit tests in Rebus.RabbitMq.Tests are failing though
Ok cool! I'll have time to look at it on Friday
ok there seem to be some issue with the internal queue in CustomQueueingConsumer.cs
. If I change it from a ConcurrentQueue
to the old SharedQueue
from https://github.com/rabbitmq/rabbitmq-dotnet-client/blob/5.x/projects/client/RabbitMQ.Client/src/util/SharedQueue.cs it seems to work better. Only 1 test is failing now..
Should be fixed by #71 🙂
using the new version of dotnet rabbitMQ client 6.1.0 seems to make rebus crash at startup in an MVC ASPNET Core 3.1 application.
using Rebus 6.3.0 and Rebus.RabbitMq 7.1.0