Skip to content

Release connection on reactive beginTransaction cancellation - #1341

Merged
injectives merged 1 commit into
neo4j:5.0from
injectives:feature/btx
Dec 1, 2022
Merged

injectives merged 1 commit into
neo4j:5.0from
injectives:feature/btx

Conversation

@injectives

Copy link
Copy Markdown
Contributor

Each transaction created by the driver requires a network connection. Unfinished transactions may result in connection leaks, meaning that connections acquired from the connection pool are not available for further use.

Subscription cancellation on reactive beginTransaction during transaction creation could result in dangling transaction, leading to the connection leak. This update fixes this issue by ensuring that such transactions are rolled back and their connections are returned to the connection pool.

Each transaction created by the driver requires a network connection. Unfinished transactions may result in connection leaks, meaning that connections acquired from the connection pool are not available for further use.

Subscription cancellation on reactive `beginTransaction` during transaction creation could result in dangling transaction, leading to the connection leak. This update fixes this issue by ensuring that such transactions are rolled back and their connections are returned to the connection pool.
@michael-simons

Copy link
Copy Markdown
Contributor

Excellent work!

image

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