Skip to content

Conversation

@bigmontz
Copy link
Contributor

The RESET should be send when a failure occurs or whenever the connection is being sent back
to the pool with a pending request running, i.e. the bolt server is not in the READY state.

These changes also affect the verifyConnectivity and getServerInfo implementation.
The RESET message is not sent in these methods if it is a newly created connection.

@bigmontz bigmontz changed the title Avoid to send reset when it is not needed Avoid sending resets when it is not needed Mar 16, 2022
@bigmontz bigmontz force-pushed the 5.0-minimal-resets branch from 4d8d5f0 to 9a540a3 Compare March 17, 2022 17:19
@bigmontz bigmontz force-pushed the 5.0-minimal-resets branch 2 times, most recently from 26529bc to dfd7af1 Compare April 12, 2022 15:45
@bigmontz bigmontz force-pushed the 5.0-minimal-resets branch from dfd7af1 to 302ff74 Compare April 22, 2022 12:14
@bigmontz bigmontz force-pushed the 5.0-minimal-resets branch from db7eae8 to 3fdf49f Compare May 5, 2022 13:05
bigmontz added 12 commits May 9, 2022 15:44
The `RESET` should be send when a failure occurs or whenever the connection is being sent back
to the pool with a pending request running, i.e. the bolt server is not in the `READY` state.

These changes also affect the `verifyConnectivity` and `getServerInfo` implementation.
The `RESET` message is not sent in these methods if it is a newly created connection.
@bigmontz bigmontz force-pushed the 5.0-minimal-resets branch from a12eaeb to 6398a1a Compare May 9, 2022 13:44
@bigmontz bigmontz merged commit cc4598b into neo4j:5.0 May 30, 2022
@bigmontz bigmontz deleted the 5.0-minimal-resets branch May 31, 2022 08:33
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.

1 participant