Replies: 1 comment
-
Hello, a small update on this, since RabbitMQ 4.0 was released a few days ago and it supports AMQP 1.0 by default: RabbitMQ log:
Even though my producer should try to connect to a specific vhost "myvhost" (where the exchange does exist). Producer properties:
is this a limitation or am I doing something wrong? thank you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
Could you tell me if smallrye-reactive-messaging-amqp used in conjunction with RabbitMQ should work when working with queues inside virtual hosts?
Note: I know there is a specific version for rabbitmq in smallrye-reactive-messaging-rabbitmq, but I would like to check if the AMQP 1.0 version of the lib would fit our needs. In addition, since RabbitMQ 4 will support AMQP 1.0 by default, the change would probably have less impacts on our applications if we could start now the with the generic lib.
I have tested with both properties
amqp-virtual-host
andmp.messaging.incoming.<mychannel>.virtual-host
in a Quarkus application, like this:But messages in the queue "myqueue" inside virtual host "myvh" are never read by my application. And if I create a queue "myqueue" in the default vhost, messages are read correctly.
In addition, my first tests for message producer / outgoing configs seem to show similar results (I get errors on RabbitMQ of the form "no exchange 'myqueue-exchange' in vhost '/' ", even though I am targetting another vhost).
Am I missing something to configure virtual hosts?
(Note: I have found this issue in Quarkus: #474 but it's closed since a long time).
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions