Cannot consume internal events published to amq.rabbitmq.events for number of bindings #12257
Replies: 1 comment
-
@eliyosef578 the internal event mechanism was never meant to be used to track e.g. definition import progress. It is meant to be used for continuous monitoring of key events, for audit purposes. Reasons can vary widely, including "the internal event mechanism needs to be initialized on boot". We will not tweak when that happens, leave alone when definitions are imported. Please use the internal event mechanism as it was designed to be used. Monitoring definition import progress on boot was never the objective. |
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
-
Following on from the previous discussion (#12053)
if i try to load the def.json with only exchange.created bindings, the events reached to the events queue.
def.json
if i try to load the definitions.json with all the 4 bindings the events are not reached to the events queue.
definitions.json
this is the rabbit log :
rabbit.log
Beta Was this translation helpful? Give feedback.
All reactions