Unexpected routing key assignment
Closed this issue · 1 comments
It seems that when several queues are being declared and bound concurrently, the routing keys (usually?) end up assigned in a very unexpected way. Here's a branch with an example binary:
https://github.com/martinslota/amqp-client/tree/routing-key-mayhem
It can be run as follows:
AMQP_HOST=<HOSTNAME> dune exec routing_key_mayhem/unleash.exe
While the binary is running, you can take a look at the bound queues:
The queues ending with endpoint1 and endpoint2 will (probably?) have swapped routing keys:
That's the unexpected part.
Note also that queues ending with endpoint3 and endpoint4 which were declared and bound sequentially have the routing keys assigned as expected.
New opam release 2.2.0 pending: ocaml/opam-repository#14571