-
Notifications
You must be signed in to change notification settings - Fork 27
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
[feature request] Missing heartbeat should trigger an I/O failure #125
Comments
Hi, indeed we can add it. |
TCP keepalive is system wide and would impact all services, whereas we can set the AMQP heartbeat per application (per connection actually!) depending on requirements. |
It does! Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the link is dropped between the client and the broker (router failure, VPN disconnect, etc…), the TCP connection remains open (Established) but nothing pass through. The heartbeat is meant to detect that condition, and we'd like to reset the connection on the client side, as the broker do on its own side of the link.
The text was updated successfully, but these errors were encountered: