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

Server failure recovery #190

Closed
wants to merge 2 commits into from
Closed

Server failure recovery #190

wants to merge 2 commits into from

Conversation

gerhard
Copy link

@gerhard gerhard commented Feb 26, 2014

No description provided.

This is rough, but it simulates one way of handling the RabbitMQ server
going away. I was suprised that I couldn't find any good examples out
there for handling this scenario. What are your thoughts on this
@michaelklishin ?
@gerhard
Copy link
Author

gerhard commented Feb 26, 2014

Somewhat related to #138, definitely related to #184. This PR is for discussion purposes-only, I am closing it as it's not a real issue.

It proved challenging to simulate and then handle rabbitmq-server becoming unavailable. This PR includes my naive implementation which proves one way of approaching it. I am very interested in hearing your thoughts on it @michaelklishin.

@gerhard gerhard closed this Feb 26, 2014
@gerhard gerhard deleted the server_failure_recovery branch February 26, 2014 14:19
@gerhard gerhard restored the server_failure_recovery branch February 26, 2014 14:19
@michaelklishin
Copy link
Member

Other clients test it by recovering from server-initiated connection.close and closing its own connection via HTTP API. Bunny should do the same.

@michaelklishin
Copy link
Member

Bunny historically has been raising an exception on the thread that instantiated the connection. This is find but for testing purposes some may want to recover instead. So this should be configurable.

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

Successfully merging this pull request may close these issues.

2 participants