-
Notifications
You must be signed in to change notification settings - Fork 73
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
During using pool in async mode with POOL_GETMODE_TIMEDWAIT see an excess of opened and busy connects over max #390
Comments
It's this place in source:
On else we create new connection by non waiting request with no respect to value of current opened connections because condition in _get_next_request push it to process:
I think we can change this to: |
The recent changes I pushed to the pool code should resolve this situation as well. Can you confirm, please? |
@golubovai python-oracledb 2.5 has the change @anthony-tuininga made. Can you try it out and let us know whether it resolves your problem? |
Hi. I have a similar situation. Updating to the latest version did not work. With long running queries, the number of connections in the pool exceeds the maximum limit. |
Can you provide more detail of your situation? What are the pool configuration parameters you are using? What are you using to determine the number of connections in the pool? Can you define "long running"? Anything else you can provide that would help determine the source of the issue? Ideally a test case that proves what you are saying would be helpful! |
Hello!
This test case can be used to clarify what is going:
The text was updated successfully, but these errors were encountered: