allow using tcp keepalives instead of heartbeats #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AMQP allows heartbeats to be disabled completely, provided the server allows that.
But it is essential to have an alternative to detect network disconnections and stale
connections. In this PR, we switch on TCP keepalives on the connection (optional but
enabled by default) and allow heartbeats to be switched off. Heartbeats are still
enabled by default though.
The
connection
method has these new parameters to allow that:heartbeat
:true
to enable heartbeat,false
to disable. Can also be set to a positive integer,in which case it is the heartbeat interval in seconds. Defaults to
true
. Iffalse
, ensurekeepalive
is enabled to detect dead connections. This parameter is negotiated with the server.keepalive
:true
to enable TCP keepalives,false
to disable. Can also be set to a positive integer,in which case it is the keepalive interval in seconds. Defaults to
DEFAULT_KEEPALIVE_SECS
.