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

crashed when change network #2

Open
leisurehuang opened this issue Jun 3, 2013 · 1 comment
Open

crashed when change network #2

leisurehuang opened this issue Jun 3, 2013 · 1 comment

Comments

@leisurehuang
Copy link

hi:

when i used the librabbitmq send message and receive, once when i back the app background,and change the network form 3g to wifi, and then go back to the app then send a message to MQ server,the app was crash by this time ,how can i resolve it ?

Thank you.

@ghost
Copy link

ghost commented Aug 26, 2014

I'm actually dealing with this right now. The issue is that when you are backgrounding and "switching connections" it invalidates the existing connection to the rabbitMQ server. So when you come out of background it will crash, hang, or any number of bad behavior.

What we do is to make absolutely sure that the connection is taken down when backgrounded, and then reestablished as a new connection on resume. This will solve your issue of the connection being invalidated, and will actually make your app a lot more robust.

Now the problem that I have is trying to get the damn thing to soft disconnect properly. The only way that we've been able to make absolutely sure that the connection gets killed on background is to call:

amqp_destroy_connection()
close(socket);

And let the server side clean up. If you have any tips or tricks you could share about how you handled this situation, it would be greatly appreciated because i'm still fighting it.

If I try to use the soft disconnect methods such as amqp_connection_close() it will sit for 30 seconds or so and then throw an unknown error -9. Which is why we just force the connection to close by closing the socket and let the server clean up the mess. Definitely not ideal in any way.

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

1 participant