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

No communication after recovery #74

Closed
neuhaus opened this issue Feb 16, 2017 · 4 comments
Closed

No communication after recovery #74

neuhaus opened this issue Feb 16, 2017 · 4 comments

Comments

@neuhaus
Copy link
Contributor

neuhaus commented Feb 16, 2017

I have a program that establishes three connections. I have configured three RabbitMQ servers.

When one of the servers goes down, the connections and channels appear to be recovered, however the communication is not working after the recovery.

I have attached a log.

recovery-log.txt

@michaelklishin
Copy link
Collaborator

I don't know about Lyra but RabbitMQ Java client does not guarantee publisher recovery: it will recover channels, topology, consumers but any concurrent publishes or other actions from applications will fail and may interfere with recovery process (cause channel exceptions as in the protocol). Clients cannot handle every possible scenario like that so developers need to make sure their applications can handle down connections and channel exceptions.

@neuhaus
Copy link
Contributor Author

neuhaus commented Feb 16, 2017

Well I switched from the normal RabbitMQ java client to Lyra to use the high availability features. It's Lyra's raison d'être.

I don't see any exceptions getting thrown. From the log it appears as if everything is recovering, however it's not working after the recovery so i guess there's a bug.

@michaelklishin
Copy link
Collaborator

There is a channel exception logged but it's impossible to tell why: only RabbitMQ logs can clarify this. There are scenarios in which neither Lyra nor automatic connection recovery in the Java client can avoid channel exceptions (the topology might have changed since connection termination, e.g. by other apps).

Without a way to reproduce there is no evidence that this is not one of those cases and it's an issue in Lyra.

@neuhaus
Copy link
Contributor Author

neuhaus commented Oct 4, 2017

Thanks for getting back to me. We have decided to migrate this project away form Lyra do the the problems with recovery so i will no longer be able to assist with this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants