-
Notifications
You must be signed in to change notification settings - Fork 871
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
OPartitionedDatabasePoolFactory returns a closed pool #4858
Comments
You should close the pool factory at the end of your application. |
Guys can not agree issue is still relevant. |
It is not needed usually to close pool at all, but if users closes it, we should do not use it any more. |
andrii0lomakin
added a commit
that referenced
this issue
Feb 22, 2016
andrii0lomakin
added a commit
that referenced
this issue
Feb 22, 2016
(cherry picked from commit da2a8ba)
Fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sample code :
After closing the pool, in the later stage of application; getting the pool from the same factory and trying to acquire a new connection reports "Pool is closed"
The OPartitionedDatabasePoolFactory retains the pool instance and returns the same, which was closed, as PoolIdentity is same.
The text was updated successfully, but these errors were encountered: