Re: ODP .Net Connection Pool Problem on Web Application

Hi all, I think I have found a reason for the problem:

The problem is caused by, when the IIS server's "executionTimeout" for httpRequest is reached, IIS will call Thread.Abort() to stop the processing thread for the Request.

For instance, If a web page is requested, meanwhile the database is very busy, the Database can't return all the result to the web application within 40 sec (the default value of executionTimeout in machine.config), this thread will be aborted!

I have just read the Release note of ODP .NET 10.2.0.1.0, in the section "TIPS, LIMITATIONS AND KNOWN ISSUES", it says:

8. Thread.Abort() should not be used, as unmanaged resources may remain unreleased properly, which can potentially cause memory leaks and hangs.

It seems that we can just avoid the problem by setting the executionTimeout value to a reasonablily large value. However, this will greatly affect the web server performance as some Threads will be hold and they are not able to serve other requests.

Please advise!

Regards,
Alex Received on Tue Feb 14 2006 - 21:35:46 CST