Oracle Data Provider for .NET: Connection request timed out
434695Dec 14 2004 — edited Jul 27 2010Hi,
We have multiple ASP.NET applications running on a server using ODP.NET (9.2.0.401) accessing a central database. One of the applications has been timing out with the following error message:
Oracle Data Provider for .NET Connection request timed out at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure) at Oracle.DataAccess.Client.OracleConnection.Open() at mcds.mcds_aircraft_serialentry.ValidateSerialNumber(String SerialNumber)
We've seen this problem before with this particular appliclation. What we did to "fix" it previously was to remove the ODP.NET DLL from the application's bin file and have it use the DLL in the system folder. This seemed to work for a few months but then we ran into the same problem. So the system guys moved the DLL back into the bin folder and everything worked again. The application continued to work for months until yesterday. We removed the DLL out of the bin folder and it appeared to be working fine. This morning, it stopped working again.
As I alluded to earlier, other ASP.NET applications using the exact same ODP.NET DLL are working fine accessing the same database and the same tables. That leads us to believe the DLL is not corrupt.
We've checked to make sure that all the connections are getting closed and destroyed in code.
We're positive its not a SQL statement that takes an extremely long time to load. On the initial page, which originally didn't even hit the database, we threw in a simple SQL statement to count the number of records in a table matching a certain record id. It even times out running that statement.
We have the same application running on a development server and it works fine, never seeing these problems.
Any suggestions as to what to try would be appreciated. We're really at a loss. One of the problems we have run into is that we have to go through a third-party to make any changes on the server and that third-party is not too keen on "trying" things without justification. We can't even get them to restart IIS!