There are no consumers for the queue defined through definitions.json file in rabbitmq in kubernetes cluster #10003
-
Describe the bugI have defined the logs queues, exchange and binding in rabbitmq configuration but when it is deployed it didn't create any exchanges and consumers for this queue. And the messages are not delivering and are piling up in the queue in rabbitmq portal. Earlier it was working fine but suddenly I got this issue. Also I have redployed the application with the same configuration but still I am facing the same issue. I don't see any abnormalities in the logs. Attaching the logs and config details. Rabbit MQ version : 3.9.14-management Below is screenshot of the logs queue in my application.
Please help me to resolve this issue. Reproduction steps1.Attaching rabbitmq deployment file and dockerfile to reproduce the issue. ... Expected behaviorWith this configuration, it should create consumers for the logs_unicast queue which I showed in the above screenshot. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Your applications add consumers. RabbitMQ (with the exception of shovels and federation links) never adds consumers to queues. It does not matter if a queue was declared by a client or created via a definitions files: your applications are responsible for registering consumers. Perhaps make sure that your apps that are supposed to consume those messages are deployed, up and running, and can connect to RabbitMQ nodes. |
Beta Was this translation helpful? Give feedback.
-
|
In other news, RabbitMQ 3.9 has reached end of life several months ago. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry to bother you, But it was working before and we do have another rabbitmq running in docker swarm, even that is configured the same way as the above and it's version is 3.8.5. Below is the screenshot of that rabbitmq application.
|
Beta Was this translation helpful? Give feedback.
-
|
@gbalamk 3.8 has reached EOL in mid-2202. Your applications connect to RabbitMQ and register consumers. If you don't have any consumers online, either they are not running or they fail to connect to the cluster. This is NOT an issue in RabbitMQ if your applications are not online or do not register consumers. |
Beta Was this translation helpful? Give feedback.
-
|
To narrow down issues with application connectivity (or startup):
From there, collecting and inspecting application logs may provide relevant clues. |
Beta Was this translation helpful? Give feedback.
Your applications add consumers. RabbitMQ (with the exception of shovels and federation links) never adds consumers to queues.
It does not matter if a queue was declared by a client or created via a definitions files: your applications are responsible for registering consumers.
Perhaps make sure that your apps that are supposed to consume those messages are deployed, up and running, and can connect to RabbitMQ nodes.