Skip to content
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.

Wrong check of assigned RabbitAdmin in getDeclaringAdmins() causing declarables to fail declaration or to be declared in the wrong broker #56

Open
rwanderc opened this issue Mar 11, 2021 · 0 comments
Assignees
Labels
bug Something isn't working v2.1.7 v2.2.3 v2.3.1

Comments

@rwanderc
Copy link
Contributor

rwanderc commented Mar 11, 2021

As per GH-18, the approach of injecting the RabbitAdmin into the setAdminsThatShouldDeclare() was changed to avoid premature initialization of the RabbitAdmin bean. The change was to inject the name of the bean instead of the real instance.
However, the check for the assignment of the RabbitAdmin was still looking for the bean and replacing the name of the bean with the latest name.
This led to failures to declare queues/exchanges/bindings or the declaration happens in the wrong broker.

Affected versions: 2.3.0, 2.2.2, 2.2.1, 2.1.5, 2.1.6

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working v2.1.7 v2.2.3 v2.3.1
Development

No branches or pull requests

1 participant