Fix liveness checking for unresponsive connections #1515
Merged
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.
Cherry-pick: #1514
The driver performs liveness checking for connections when remove them from the pool.
When this connections are not responsive, the driver hangs waiting for the result of the
SUCCESS
message get back.This problem occurs becaue driver are not taking in consideration the connection hint
connection.recv_timeout_seconds
in the liveness check routinge.The problem is solved by add the ConnectionReadTimeoutHandler to the pipeline also in case of liveness check ping.
Remove unused imports
apply code style
Update driver/src/main/java/org/neo4j/driver/internal/async/pool/NettyChannelHealthChecker.java