Closed dsennerlov closed 4 years ago
There is no such thing as "connecting to queues". Connections are not affected by the queue property equivalence requirement.
I cannot suggest anything without server logs or a traffic capture. As of https://github.com/rabbitmq/rabbitmq-common/issues/341 (RabbitMQ 3.8.2
) a missing x-queue-mode
is treated as the same as setting it to "classic".
If you have a set of steps to reproduce and a known solution, please submit a PR instead of recommending monkey patches.
@dsennerlov can you please confirm that master works for your existing installation?
This is the right moment to make any changes we want in this area as the next release will be a 1.0.0
(it's as good a time as any to ship it after several years worth of releases and production usage).
@michaelklishin Confirmed, problem is solved in latest master.
Thanks. I will produce a 1.0
most likely in the next 24 hours.
Problem
Existing queues, that where created with Hutch 0.27.0 have a
queue_mode
set tonone
, and the new defaultqueue_mode
implementation in Hutch makes it impossible to connect to these queues. Only way to setqueue_mode
tonone
is to not send thex-queue-mode
argument.Offending commit and lines
1f56c25 (#341)
Solution
This monkey patch will fix the problem:
The fix is to add
if @queue_mode
andif @queue_type
to have an option to not send the arguments.This will allow me to set
@queue_mode = nil
and@queue_type = nil
and get everything working.