Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Regression: Connections for Neo4J not being returned #223

Closed
ifadams opened this issue Oct 3, 2024 · 0 comments · Fixed by #224
Closed

Regression: Connections for Neo4J not being returned #223

ifadams opened this issue Oct 3, 2024 · 0 comments · Fixed by #224
Assignees
@ifadams
Labels
Bug Indicates unexpected or undesired behaviors
Milestone
v2.10.0 Tasks

Comments

@ifadams
Copy link
Contributor

ifadams commented Oct 3, 2024

Describe the bug

Currently the internals of VDMS are not correctly returning used connections to Neo4J, causing a hard-limit to occur on the number of sequential transactions that are allowed.

To Reproduce

Issue more than 16 VDMS transactions in a row.

Expected behavior

Internally, connections should be returned and re-used after transaction commit.
@ifadams ifadams added the Bug Indicates unexpected or undesired behaviors label Oct 3, 2024
@ifadams ifadams added this to the v2.10.0 Tasks milestone Oct 3, 2024
@ifadams ifadams self-assigned this Oct 3, 2024
@ifadams ifadams linked a pull request Oct 3, 2024 that will close this issue
connection pool bug fix #224
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ifadams ifadams

Labels
Bug Indicates unexpected or undesired behaviors
Projects
None yet
Milestone
v2.10.0 Tasks
Development

Successfully merging a pull request may close this issue.

connection pool bug fix IntelLabs/vdms
1 participant
@ifadams