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

Reconnect on failures #3

Open
justinweiss opened this issue May 12, 2011 · 3 comments
Open

Reconnect on failures #3

justinweiss opened this issue May 12, 2011 · 3 comments

Comments

@justinweiss
Copy link
Owner

From the xmpp4r docs:

If you want your connection to survive disconnects and timeouts, catch exception in Stream#on_exception and re-call Client#connect and Client#auth. Don‘t forget to re-send initial Presence and everything else you need to setup your session.

@ajsharp
Copy link

ajsharp commented Sep 27, 2011

Big +1. I may take a crack at this this week.

@justinweiss
Copy link
Owner Author

I fixed by far our most common crash (UTF-8 characters) but this would still be really nice to have.

@stevenharman
Copy link
Contributor

I've got Robut running on a MacMini in our office. We're using launchd to make sure Robut runs when the system boots, and restart it on failure, etc...

However, Robut will occasionally get disconnected (not sure why, and nothing shows up in the logs), and then I have to manually restart the service to get it to reconnect. Launchd doesn't help here as it the service doesn't "fail", it just disconnects. Auto-reconnecting on failure would go a long way to keeping our Robut up and running.

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

3 participants