Replies: 3 comments 3 replies
-
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
From .NET client guide's Concurrency Considerations section:
So yes, you are doing something wrong. Concurrent publishing on a shared channel was always explicitly not supported |
Beta Was this translation helpful? Give feedback.
-
Hello everyone who has commented here - If you have time to test version 7 alphas, it would be really appreciated https://www.nuget.org/packages/RabbitMQ.Client/7.0.0-alpha.6 I'm hoping to get the final release done this month, but only if there is enough community testing (with reports back!) |
Beta Was this translation helpful? Give feedback.
-
Hi,
one test in our code base - that was previously working - doesn't work anymore. N messages were published - correctly - over the MQ and then consumed by a consumer components (the component under test). After upgrading RabbitMQ and also the client the messages were not published anymore. Did the #878 introduced a change? Am I doing something wrong?
Expectations: all messages are published and confirmed and available to be consumed.
Results: few messages are published and confirmed, few messages are not confirmed and many get exceptions on publish.
Here the tests:
RabbitMQ instance
RabbitMQ logs
dotnet --info
Beta Was this translation helpful? Give feedback.
All reactions