You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: