Skip to content

Conversation

bigmontz
Copy link
Contributor

The previous implementation of the timeout was not considering if requests were being treated by the server or not.
This behaviour causes connections being wrongly close by inactivity.

For fixing this issue, the timeout configuration changed to only be applied whenever there are ongoing requests.

The previous implementation of the `timeout` was not considering if requests were being treated by the server or not.
This behaviour causes connections being wrongly close by inactivity.

For fixing this issue, the `timeout` configuration changed to only be applied whenever there are ongoing requests.
@bigmontz bigmontz merged commit 7eb5d43 into neo4j:4.4 Mar 24, 2022
@bigmontz bigmontz deleted the 4.4-fix-receive-timeout branch March 24, 2022 11:21
bigmontz added a commit to bigmontz/neo4j-javascript-driver that referenced this pull request Mar 24, 2022
The previous implementation of the `timeout` was not considering if requests were being treated by the server or not.
This behaviour causes connections being wrongly close by inactivity.

For fixing this issue, the `timeout` configuration changed to only be applied whenever there are ongoing requests.
bigmontz added a commit that referenced this pull request Mar 24, 2022
The previous implementation of the `timeout` was not considering if requests were being treated by the server or not.
This behaviour causes connections being wrongly close by inactivity.

For fixing this issue, the `timeout` configuration changed to only be applied whenever there are ongoing requests.
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

Successfully merging this pull request may close these issues.

2 participants