First pooled connection fails when using UseHourOffsetForUnsupportedTimezone #429
Comments
|
I've created Bug 37419098 to track this issue. |
|
@Aaron-Ritter-IDEXX Can you provide the full ODP.NET trace? You can either post it to this thread or email it to dotnet_us(at)oracle.com. |
|
@Aaron-Ritter-IDEXX This is a reminder to provide the full ODP.NET trace so that the ODP.NET dev team can debug the issue. |
|
Thanks, and sorry for the delay. I went on a long vacation just before you responded. I meant to check in on this occasionally, but I got caught up in the festivities and forgot about it. I have emailed a full log, since it contains data that I'd rather not make public. |
|
Come to think of it, I believe we encountered the same problem in the |
|
@alexkeh a reminder that this is open |
|
I've asked the developer reviewing the issue for an update. I'll let you know what he says when he reports back. |
|
@Aaron-Ritter-IDEXX My team has been unable to reproduce the problem with your setup details so far. However, we have an idea of what the problem is and created a combination diagnostic fix. The fix may work, but if not, it includes enhanced diagnostics for us to diagnose it better. We cannot distribute diagnostic software via NuGet Gallery. Can you open up an Oracle Support service request? If you don't know how, your DBA does. Once the SR is open, inform the support analyst you are hitting bug 37419098 and working with me directly on the Oracle DB ODP.NET team. The analyst can then give you access to the diagnostic fix that will be part of the bug log. The problem will be resolved or not. If resolved, we'll incorporate the fix into the ODP.NET code line. If not, you'll share the enhanced diagnostics and upload those to the SR for us to analyze and we'll give you a new drop to validate. |
|
@alexkeh Alright, sounds like a good plan. I'll ask our DBA team to get it started. |
|
FYI, I was told earlier in the week that the build is "in processing" and am waiting for further updates. |
|
We had some problems building the diagnostic fix. I think they were resolved. We should have the possible fix available to try out soon. |
I'm using the
Oracle.ManagedDataAccess.Corepackage version 23.6.1 (though this problem seems to be present in older versions as well) and trying to connect to a v.19c database with an old time zones file (v.14) from a system set to the UTC time zone. The first attempt to connect always fails with a "connection timeout", while subsequent attempts succeed.It fails at first because the "Etc/UTC" zone isn't available in the database. Now, I have the
UseHourOffsetForUnsupportedTimezoneoption enabled, so it then retries using the hour offset, but that fails due to aNullReferenceExceptioninside the package code, and then the attempt to get a connection from the pool eventually times out.Of course, we could try to update the database's time zone file, but this seems to be a potential bug in the package, so I'd like to discuss this first.
Here are some relevant parts from the trace log:
Finally, here's where it starts to retry the connection using the hour offset, which fails:
Note the
NullReferenceExceptiondeep inTTCAuthenticate. This seems to be out of my control. Note also that the final (TIMEOUT) log line is from 45 seconds later; I have the connection timeout set to 45 seconds.The text was updated successfully, but these errors were encountered: