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
No automatic recovery #10
Comments
Good catch. Thanks for reporting. I'm working on it. |
Same exception here +1 One possible solution may be to put shutdown listener and try to reconnect |
@iozozturk wrote:
No, is not. You can always help if you feel that some feature is missing.
Configuration option for automatic recovery has been added here: a9c0540 |
I've posted #36 what is first step toward fixing this, but is rather independent of further change that has to be done. Namely I think that QueueSubscription should not signal |
+1 |
1 similar comment
+1 |
I've made it work, check: #49 |
One gotcha here is that the underlying amqp Java library will not try to recover the initial connection attempt[1]:
[1] https://www.rabbitmq.com/api-guide.html#connection-recovery-triggers |
I gave this template a try: http://typesafe.com/activator/template/rabbitmq-akka-stream
I start the app with activator run, then kill the rabbitmq server and start it back up again. Nothing happened even though I have the setting recovery-interval = 5s. Am I missing something?
I tried debugging it and saw that you never set factory.setAutomaticRecoveryEnabled(true). Doing that helps, but there are still issues with "com.rabbitmq.client.AlreadyClosedException: channel is already closed due to clean channel shutdown".
The text was updated successfully, but these errors were encountered: