Cannot consume internal events published to amq.rabbitmq.events #12053
-
Describe the bughey, Reproduction steps1.init "rabbitmq-event-exchang" with Enabled Plugins File Expected behaviorthe events are delivered to the queue as expected. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
@eliyosef578 that exchange type hasn't changed meaningfully in years. I don't see how re-configured plugin list would be different from manually enabled plugins. There are so many systems that pre-configure plugins these days that we'd be flooded with questions like that but it is not the case. My best guess is that your Consider posting your |
Beta Was this translation helpful? Give feedback.
-
|
Given the following [rabbitmq_management,rabbitmq_event_exchange].and a 3.13.5 node started like so RABBITMQ_ENABLED_PLUGINS_FILE=./enabled_plugins rabbitmq-serverI see the following in the Then I bind a quorum queue with routing key # open a connection and channel first, then…
qq = ch.quorum_queue("qq.1")
qq.bind("amq.rabbitmq.event", routing_key: "#").subscribe do |*args|
puts(args.inspect)
endand then declare and delete 100 queues: 100.times { |i| ch.queue("cq.transient.#{i}", durable: false).delete }the consumer does print them out, and then prints a I can also see the following in @eliyosef578 without clear evidence (an executable way reproduce) and the lack of other similar reports, I can only conclude that most likely your new environment
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @michaelklishin thanks for your response. the docker run command is: the event exchange plugin its enabled and the queue and the binding are created after the init, but the events do not reach to the queue. if i try to runnig the docker without enabled_plugins file And I do the enable manually the events reach to the queue. |
Beta Was this translation helpful? Give feedback.
-
|
@eliyosef578 I have demonstrated that the exchange works as expected and explained what the two most typical problems are. Take a look at your definitions file. You have bindings that do not have any routing key, which is critically important for topic exchanges such as "bindings": [
{
"source": "amq.rabbitmq.event",
"vhost": "/",
"destination": "qq.1",
"destination_type": "queue",
"routing_key": "#",
"arguments": {}
}and an extract from your "bindings": [
{
"source": "amq.rabbitmq.event",
"vhost": "/",
"destination": "events",
"destination_type": "binding.created",
"arguments": {}
},
{
"source": "amq.rabbitmq.event",
"vhost": "/",
"destination": "events",
"destination_type": "exchange.created",
"arguments": {}
},
{
"source": "amq.rabbitmq.event",
"vhost": "/",
"destination": "events",
"destination_type": "binding.deleted",
"arguments": {}
}
]Your bindings have an invalid destination type, the supported values are My best guess is that you have hand-crafted these definitions. They cannot possibly work (or even pass validation before being imported) regardless of how you enable the plugin. |
Beta Was this translation helpful? Give feedback.
-
|
@michaelklishin You are right, I attached the wrong definitions file. |
Beta Was this translation helpful? Give feedback.
-
|
@michaelklishin i try to debug with 2 kind of definitions files : |
Beta Was this translation helpful? Give feedback.
-
|
Definitions are imported after plugins are enabled. You can always import definitions after cluster formation using CLI tools. With one node it can be a matter of using |
Beta Was this translation helpful? Give feedback.
Given the following
enabled_pluginsfile:and a 3.13.5 node started like so
I see the following in the
rabbitmq-diagnostics statusoutput:Then I bind a quorum queue with routing key
#(which, for a topic exchange likeamq.rabbitmq.event, matches everything) to it, using Bunny for client and a Ruby REPL as an alternative to writing a script:# open a co…