Skip to content

[4.4] Harden driver against unexpected RESET responses #1042

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Apr 12, 2024

Conversation

robsdedude
Copy link
Member

The server has been observed to reply with FAILURE and IGNORED to RESET requests. The former is according to spec and the driver should drop the connection (which it didn't), the latter isn't.

The right combination of those two unexpected responses at the right time could get the driver stuck in an infinite loop.

This change makes the driver drop the connection in either case to gracefully handle the situation.

Backport of: #1006

The server has been observed to reply with `FAILURE` and `IGNORED` to `RESET`
requests. The former is according to spec and the driver should drop the
connection (which it didn't), the latter isn't.

The right combination of those two unexpected responses at the right time could
get the driver stuck in an infinite loop.

This change makes the driver drop the connection in either case to gracefully
handle the situation.
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴

@robsdedude robsdedude merged commit 356c829 into neo4j:4.4 Apr 12, 2024
12 checks passed
@robsdedude robsdedude deleted the harden-agains-failing-reset-4.4 branch April 12, 2024 10:22
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants