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

.

Relevant Pages

  • Re: ASP.Net application recycling problem
    ... > Eventually IIS recycles our application due to deadlock condition. ... Each request produces the following error: ... > Currently we don't have any idea about the reason of such behavior. ... > process isolation level - Medium ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ODP .Net Connection Pool Problem on Web Application
    ... I think I have found a reason for this problem: ... when the IIS server's "executionTimeout" for ... IIS will call Thread.Abortto stop the ... processing thread for the Request. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ODP .Net Connection Pool Problem on Web Application
    ... I have find some reason for the problem. ... when the IIS server's "executionTimeout" for ... IIS will call Thread.Abortto stop the ... processing thread for the Request. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Execution Timeout Problem
    ... The browser really is the ultimate problem here, since it can choose to abandon the request. ... shouldn't I be able to use the executionTimeout attribute of the element to control these timeouts? ... Sometimes the total execution time can take 2-3 minutes, but even though I have set the executionTimeout in web.config to a high number of seconds, the request will still time out after 90 seconds. ...
    (microsoft.public.dotnet.framework.aspnet)