You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have ran into the issue when configuring Camel endpoint for RabbitMQ queue that was configured with 'x-ha-policy=all' parameter.
When system starts up and queue is being defined based on the endpoint I get following exception.
channel error; reason: {#method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-ha-policy' for queue 'test.queue' in vhost '/': received none but current is the value 'all' of type 'longstr', class-id=50, method-id=10),null,""}
Looks like RabbitMQ connection requires endpoint queue parameters to match those defined on the queue itself. This is fine, however, looking at the documentation and the code 'x-ha-policy' argument is not supported and is not being passed to connection code.
Please let me know the best way to address this issue. Am I overlooking something? Should I wait for a fix or fork the code, make a fix and submit it for review?
Thanks,
Yury
The text was updated successfully, but these errors were encountered:
Hi,
I have ran into the issue when configuring Camel endpoint for RabbitMQ queue that was configured with 'x-ha-policy=all' parameter.
When system starts up and queue is being defined based on the endpoint I get following exception.
channel error; reason: {#method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-ha-policy' for queue 'test.queue' in vhost '/': received none but current is the value 'all' of type 'longstr', class-id=50, method-id=10),null,""}
Looks like RabbitMQ connection requires endpoint queue parameters to match those defined on the queue itself. This is fine, however, looking at the documentation and the code 'x-ha-policy' argument is not supported and is not being passed to connection code.
Please let me know the best way to address this issue. Am I overlooking something? Should I wait for a fix or fork the code, make a fix and submit it for review?
Thanks,
Yury
The text was updated successfully, but these errors were encountered: