Skip to content

Handle AuthorisationExpired during rediscovery #803

New issue

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

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

Already on GitHub? Sign in to your account

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Nov 1, 2021

The connections to a server should not be sent back to the pool if an AuthenticationExpired failure happens.

Sending the connection back to the pool will make the next work using the connection fails with the same error.

Testing: neo4j-drivers/testkit#288

The connections to a server should not be sent back to the pool if an AuthenticationExpired failure happens.

Sending the connection back to the pool will make the next work using the connection fails with the same error.
@bigmontz bigmontz force-pushed the 4.4-handle-athorization-expired-in-routing-connection branch 2 times, most recently from ac20a05 to b29c48a Compare November 2, 2021 15:17
Copy link
Member

@robsdedude robsdedude left a comment

Choose a reason for hiding this comment

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

🔖

@bigmontz bigmontz force-pushed the 4.4-handle-athorization-expired-in-routing-connection branch from b29c48a to c7c1424 Compare November 2, 2021 16:22
@bigmontz bigmontz merged commit 5ad3424 into neo4j:4.4 Nov 3, 2021
@bigmontz bigmontz deleted the 4.4-handle-athorization-expired-in-routing-connection branch November 3, 2021 09:22
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