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.

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

Connection Pool - Broken Connection Handling [DNET916] #843

Closed
firebird-automations opened this issue Nov 8, 2019 · 2 comments
Closed

Connection Pool - Broken Connection Handling [DNET916] #843

firebird-automations opened this issue Nov 8, 2019 · 2 comments
Assignees
@cincuranet
Labels
component: ado.net provider fix-version: 7.5.0.0 priority: major resolution: fixed/done type: bug

Comments

@firebird-automations
Copy link

Submitted by: Patrick Frießnegg (trynn)

Issue still not solved.
Depending on FbConnectionInternal.Database.ConnectionBroken state - the problem is partially fixed.

Dead connections does not get back in "available" queue if ConnectionBroken is set, but they get stuck in "busy" queue now.
Therefore, with each broken connection the connection pool is reduced by 1.
Leading to a dead application / "connection pool is full" which the code does not recover from.

related to
DNET585
DNET818
DNET668

Commits: ccb602a
@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: In Progress [ 3 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: vNext [ 10915 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cincuranet cincuranet

Labels
component: ado.net provider fix-version: 7.5.0.0 priority: major resolution: fixed/done type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cincuranet @firebird-automations