-
Notifications
You must be signed in to change notification settings - Fork 644
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
AMQP cached connection provider does not reconnect #3023
Labels
Comments
Thank you for pointing this misbehaviour out. |
bturos
added a commit
to bturos/alpakka
that referenced
this issue
Oct 19, 2023
Merged
bturos
added a commit
to bturos/alpakka
that referenced
this issue
Oct 19, 2023
bturos
added a commit
to bturos/alpakka
that referenced
this issue
Oct 19, 2023
ennru
pushed a commit
that referenced
this issue
Oct 20, 2023
Fixed with #3025 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! First of all, thanks for all the hard work on developing the Alpakka. We're using it on daily basis in our project and it's very useful 🙂
Also, this is my first issue submission, if there's anything wrong or missing, please let me know
Versions used
Akka version:
2.8.4
Alpakka AMQP:
6.0.2
Expected Behavior
With restartable AMQP source, when server side closes the connection, client should attempt to reconnect
Actual Behavior
When using
AMQPCachedConnectionProvider
, once server closes the connection, client is unable to reconnect properlyRelevant logs
Reproducible Test Case
The simplest I could come up with is the following (note: I tested with local RabbitMQ instance):
I think this is a regression introduced here: https://github.com/akka/alpakka/pull/2959/files
Looks like after this update, internal provider is never asked to open a new connection again. I might be misunderstanding the idea though, feel free to correct me.
ℹ️ The same logic is working with Alpakka 5.0
I'll be happy to open a PR for this, if you think this is an actual issue (as a novice here I might need some guidance though 🙂 )
Cheers!
The text was updated successfully, but these errors were encountered: