Fix flaky RabbitMQ integration tests #21061
Conversation
In RabbitMQ queues are what store messsages for processing, while exchanges are what messages are sent to. If an exchange has no bound queues, in most standard cases, any messages sent to the exchange are dropped. The "incoming" RabbitMQ connector is what creates and binds a queue to an exchange. This fix adds a delay to the "outgoing" messages to ensure the "incoming" connector has time to create and bind the required queue to the required exchange.
|
@geoand @cescoffier This should fix the issue with RabbitMQ integration tests. Basically it just needs time to make sure the queue is bound to the exchange before sending messages. @cescoffier My testing has shown that the multi-connect issue fixed via smallrye/smallrye-reactive-messaging#1447 happens nearly every time for outgoing connectors. Any idea when SR RM RabbitMQ 3.11.0 will be released so we can update the Quarkus dependency to include this fix? |
|
@stuartwdouglas I was the also working to fix the tests. This is essentially the same fix as you are testing in #21056. You can read the above explanation as to why this is needed for RabbitMQ. |
|
Thanks! |
|
@kdubb @ozangunalp 3.11 will be in Quarkus 2.5 so mid-november. |
|
Release planning: https://github.com/quarkusio/quarkus/wiki/Release-Planning#25 |
In RabbitMQ queues are what store messsages for processing, while exchanges are what messages are sent to. If an exchange has no bound queues, in most standard cases, any messages sent to the exchange are dropped.
The "incoming" RabbitMQ connector is what creates and binds a queue to an exchange. This fix adds a delay to the "outgoing" messages to ensure the "incoming" connector has time to create and bind the required queue to the required exchange.