Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RMQConnectionManager must be scoped to the child container #162

Closed
derevnjuk opened this issue Jun 27, 2023 · 0 comments · Fixed by #163
Closed

RMQConnectionManager must be scoped to the child container #162

derevnjuk opened this issue Jun 27, 2023 · 0 comments · Fixed by #163
Assignees
Labels
Type: bug Something isn't working

Comments

@derevnjuk
Copy link
Member

When creating a repeater, we are currently reusing a global instance of RMQConnectionManager. This approach is causing unexpected behavior and may lead to potential issues.

Steps to Reproduce:

  1. Create two repeaters using the RepeaterFactory.
  2. Perform operations or actions on the repeater.

Expected Behavior:
The repeater should function correctly, using a scoped RMQConnectionManager instance specific to the repeater with the proper credentials.

Actual Behavior:
Due to the reuse of the global instance of RMQConnectionManager, the repeater may encounter unexpected behavior, such as incorrect handling of auth.

@derevnjuk derevnjuk added the Type: bug Something isn't working label Jun 27, 2023
@derevnjuk derevnjuk self-assigned this Jun 27, 2023
derevnjuk added a commit that referenced this issue Jun 27, 2023
derevnjuk added a commit that referenced this issue Jun 27, 2023
derevnjuk added a commit that referenced this issue Jun 27, 2023
derevnjuk added a commit that referenced this issue Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment