Hello Scott.
Try to set the responseDeadLoc kInterval attribute to Infinite. Does this
work?
A crash dump will tell why there is a deadlock. To do the dump you need to
use ADPlus.
For more information on this check out:
286350 HOW TO: Use ADPlus to Troubleshoot "Hangs" and "Crashes"
http://support.microsoft.com/?id=286350
You might be running into the same problem as described in
Q321792 ASP.NET Worker Process (Aspnet_wp.exe) Is Recycled Unexpectedly
http://support.microsoft.com/default...;EN-US;Q321792
Are you using static OledbConnection s?
Please let me know what happens with these troubleshooting steps.
Thanks,
Bassel Tabbara
Microsoft, ASP.NET
This posting is provided "AS IS", with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Scott Dever" <sc****@logansr oadhouse.com>
| Sender: "Scott Dever" <sc****@logansr oadhouse.com>
| References: <8b************ *************** *@phx.gbl>
<c5************ **@cpmsftngxa09 .phx.gbl>
| Subject: RE: Maching.config responsedeadloc kinterval
| Date: Wed, 9 Jul 2003 12:04:36 -0700
| Lines: 122
| Message-ID: <05************ *************** *@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNGTPBbi2Tp37Y bSji+CkVdty/KsA==
| Newsgroups: microsoft.publi c.dotnet.framew ork.aspnet
| Path: cpmsftngxa06.ph x.gbl
| Xref: cpmsftngxa06.ph x.gbl microsoft.publi c.dotnet.framew ork.aspnet:1580 89
| NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
| X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.aspnet
|
| Hello,
| Thanks for the feedback. The odd thing is that there is
| no error reported in the event viewer of either the web
| server or the SQL Server. I might be looking at the
| wrong setting. After ~1 hour the user gets a page in
| their browser that says - "page cannot be displayed".
| They do not get an error message.
|
| Let me know what you think.
|
| Thanks!
| >-----Original Message-----
| >Hello Scott,
| >Did you increase the value of the <executionTimeo ut>
| parameter?
| >You can also tune the following parameters in your
| Machine.config file to
| >best fit your situation:
| >
| >- <maxWorkerThrea ds>
| >- <maxIoThreads >
| >- <minFreeThreads >
| >- <minLocalReques tFreeThreads>
| >- <maxconnectio n>
| >- <executionTimeo ut>
| >
| >Do you have your application associated with version 1.1
| of the framework?
| >
| >To configure the application to use ASP.NET 1.0, follow
| these steps:
| >
| >
| >1. Click "Start", and then click "Run".
| >
| >2. In the "Open" text box, type "cmd", and then
| click "OK".
| >
| >3. At the command prompt, locate the following directory:
| >
| >
| >
| <WindowsDirecto ry>\Microsoft.N ET\Framework\v1 .0.37
| 05\
| >
| >4. At the command prompt, type one of the following
| commands:
| >
| > - To Install ASP.NET 1.0 recursively
| >
| >
| > "aspnet_reg iis -s
| W3SVC/1/ROOT/AspVerApp1" (without the quotation marks)
| > -or-
| > - To Install ASP.NET 1.0 non-recursively
| >
| >
| > "aspnet_reg iis -sn
| W3SVC/1/ROOT/AspVerApp1" (without the quotation marks)
| >
| >For more information on deadlocks check the following kb
| article on how to
| >resolve this problem:
| >821268 PRB: Contention, Poor Performance, and Deadlocks
| When You Make Web
| >
http://support.microsoft.com/?id=821268
| >
| >This might give you a solution for 1.1.
| >
| >
| >Thanks,
| >Bassel Tabbara
| >Microsoft, ASP.NET
| >
| >This posting is provided "AS IS", with no warranties,
| and confers no rights.
| >
| >
| >
| >--------------------
| >| Content-Class: urn:content-classes:message
| >| From: "scott dever" <sc****@logansr oadhouse.com>
| >| Sender: "scott dever" <sc****@logansr oadhouse.com>
| >| Subject: Maching.config responsedeadloc kinterval
| >| Date: Tue, 8 Jul 2003 10:04:42 -0700
| >| Lines: 13
| >| Message-ID: <8b************ *************** *@phx.gbl>
| >| MIME-Version: 1.0
| >| Content-Type: text/plain;
| >| charset="iso-8859-1"
| >| Content-Transfer-Encoding: 7bit
| >| X-Newsreader: Microsoft CDO for Windows 2000
| >| Thread-Index: AcNFcwZTUsba4Gx dSsqhYCiJq33NAw ==
| >| X-MimeOLE: Produced By Microsoft MimeOLE
| V5.50.4910.0300
| >| Newsgroups: microsoft.publi c.dotnet.framew ork.aspnet
| >| Path: cpmsftngxa09.ph x.gbl
| >| Xref: cpmsftngxa09.ph x.gbl
| microsoft.publi c.dotnet.framew ork.aspnet:3306 7
| >| NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
| >| X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.aspnet
| >|
| >| In .NET framework 1.0 I had the
| responseadelock interval
| >| set to 1:30 (1 hour 30 minutes) to allow for some long
| >| running queries to finish on certain pages of an
| ASP.NET
| >| application. After upgrading to framework 1.1 the
| >| setting seems to be ignored and the applications
| >| deadlocks at one hour. The user gets a page on their
| >| browser that says - Unable to display the page. The
| >| query is still running on the SQL Server. I am
| running
| >| IIS 5.0.
| >|
| >| Am I missing a setting somewhere else?
| >|
| >| Thanks
| >|
| >
| >.
| >
|
