-
Notifications
You must be signed in to change notification settings - Fork 191
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
Deadlock in in OracleConnectionDispenser.ProcessInstanceUp() #401
Comments
Was this behavior observed after an ODP.NET upgrade, meaning the same code ran without a deadlock with the earlier ODP.NET version? If so, what was the version? Is this ODP.NET Core or managed ODP.NET? Since this problem isn't reproducible on another system, I recommend opening up a service request with Oracle Support. Typically, we'll need to collect further diagnostics to determine the root cause. And the only way that would be possible is to run those diagnostics in the environment with the problem. |
We've been on 21.14.0 since May 1st and had no issues since then. This was only a one time thing. We have never seen it afterwards so I cannot offer more information than the memory dump I created when the deadlock was happening. |
I still recommend the Oracle Support SR route if you want to get the dump analyzed. The Oracle Support team has the most experience with working with memory dumps. |
Closing. The next step is to open an SR for Oracle Support to analyze the dump and collect more diagnostics. |
Hi,
we're at oracle.manageddataaccess 21.14.0 and just experienced a deadlock during parallel
OracleConnection.Open()
. The stacks of three threads:I also have a process dump (zipped around 300MB) at the deadlock if you want me to send it (on private channels).
Not reproducible.
The text was updated successfully, but these errors were encountered: