This repository has been archived by the owner on Feb 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 32
New Queues, Exchanges, Bindings not been created. #54
Comments
Thank @ocristian for opening the issue. That's fixed in |
rwanderc
added a commit
that referenced
this issue
Mar 9, 2021
rwanderc
added a commit
that referenced
this issue
Mar 11, 2021
rwanderc
added a commit
that referenced
this issue
Mar 11, 2021
rwanderc
added a commit
that referenced
this issue
Mar 11, 2021
ocristian
added a commit
that referenced
this issue
May 19, 2021
…r bindings. (#63) It was being overwritten, as we were using its reference instead of a new instance. In addition, the bean name was being set after calling afterPropertiesSet, which caused the registered bean to have no name. Those two problems cause that during the declaration of the queues,exchange or bindings, the registered RabbitAdmin was not identified as DeclarableAdmins. RabbitAdmin filter the declarebles here: RabbitAdmin.filterDeclarables(.....) and the admin checks here: declarableByMe(...) Introducing Github Actions to build, release and publishing artifacts to maven central
Issue fixed on release v2.4.0. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Queues, exchanges or bindings not existing in the broker yet are not being automatically created when using
@RabbitListener
.A possible root cause for it is because we have specific
declaringAdmins
, in those declarebles created by MultiRabbit.This info is evaluated by RabbitAdmin while filtering the declarables.
Here, we can see the obj status during that evaluation.
Queue
declaringAdmins
is different thanthis.beanName
The text was updated successfully, but these errors were encountered: