-
Notifications
You must be signed in to change notification settings - Fork 80
DPY -4011 even after setting up TLS #482
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
Comments
Can you share the traceback? Using a standalone script that creates a standalone connection to the database will be helpful in determining the source of the issue. |
I will get the traceback soon. We face the issue intermittently so I will work on getting the traceback soon. |
I got a traceback from the logs for one of the services which were running. We are using SQLAlchemyORM and GraphQL GraphQL request:4:3 The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
It's the server dropping the connection; do you have any DB traces? We can access them via an SR or email, if you like. |
We did not have any traces in DB with this particular error. Is there any trace that we can set in the front end so that it can generate the traces in the DB? |
I am getting DPY 4011 issue even after setting up TLS connection to the database. I am currently using python-oracledb=3.1.0 and it is connecting to oracle 19c. I am using it in Thin mode. We are using in a service deployed in K8s connecting to an on premise Oracle Database. Python version 3.12.
My create pool setup and parameters are as follows
MIN_POOL=1
MAX_POOL=5
INCREAMENT= 1
TIMEOUT=300
EXPIRE_TIME = 60
RETRY_COUNT=3
RETRY_DELAY=5
disable_oob=True
Is there any trace that I can setup any trace to check the cause of the issue? Are there any specific parameters to help mitigate this issues?
The text was updated successfully, but these errors were encountered: