| Groups | Blog | Home |
dotnet performance : ASP.NET Deadlocks
essentially lock up the ability to run the applications. I have browsed the support articles and they all seem to apply to the 1.0 framework and advise a hotfix to correct the issue. But we are running the 1.1 Framework. The articles suggest changing the timing of the responseDeadlockInterval setting, but don't say whether to increase it or decrease it. So which is it? Any help would be greatly appreciated. Event Type: Error Event Source: ASP.NET 1.1.4322.0 Event Category: None Event ID: 1003 Date: 8/22/2003 Time: 2:53:32 PM User: N/A Computer: WEBSERVER Description: aspnet_wp.exe (PID: 3208) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last 300 seconds. This timeout may be adjusted using the <processModel responseDeadlockInterval> setting in machine.config. -- Martin Blackstone MVP - Exchange http://www.swinc.com/resource/exchange.htm http://www.swinc.com/resource/e2kfaq_appxc.htm
responseDeadlockInterval:
Specifies the time interval, in standard process model format (hr:min:sec), after which the process will be restarted if the following conditions are met: a.. There are queued requests. b.. There has not been a response during this interval. The default is 3 minutes. "Martin Blackstone [MVP - Exchange]" <martinb@myrealbox.com> wrote in message news:eQN8EQYaDHA.2072@TK2MSFTNGP10.phx.gbl... [quoted text, click to view] > We are seeing a lot of errors like the one below which when occur > essentially lock up the ability to run the applications. > I have browsed the support articles and they all seem to apply to the 1.0 > framework and advise a hotfix to correct the issue. But we are running the > 1.1 Framework. > > The articles suggest changing the timing of the responseDeadlockInterval > setting, but don't say whether to increase it or decrease it. > So which is it? > > Any help would be greatly appreciated. > > > Event Type: Error > Event Source: ASP.NET 1.1.4322.0 > Event Category: None > Event ID: 1003 > Date: 8/22/2003 > Time: 2:53:32 PM > User: N/A > Computer: WEBSERVER > Description: > aspnet_wp.exe (PID: 3208) was recycled because it was suspected to be in a > deadlocked state. It did not send any responses for pending requests in the > last 300 seconds. This timeout may be adjusted using the <processModel > responseDeadlockInterval> setting in machine.config. > > -- > Martin Blackstone > MVP - Exchange > > http://www.swinc.com/resource/exchange.htm > > > http://www.swinc.com/resource/e2kfaq_appxc.htm > >
ISAPI and Worker Process Isolation Mode.
This might help, I meant to send with first reply. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/iisref/htm/ISAPIAndWorkerProcessIsolationMode.asp [quoted text, click to view] "MS News (MS ILM)" <sql_agentman@hotmail.com> wrote in message news:eVurqvbaDHA.1600@TK2MSFTNGP09.phx.gbl... > responseDeadlockInterval: > > Specifies the time interval, in standard process model format (hr:min:sec), > after which the process will be restarted if the following conditions are > met: > a.. There are queued requests. > b.. There has not been a response during this interval. > The default is 3 minutes. > > > > "Martin Blackstone [MVP - Exchange]" <martinb@myrealbox.com> wrote in > message news:eQN8EQYaDHA.2072@TK2MSFTNGP10.phx.gbl... > > We are seeing a lot of errors like the one below which when occur > > essentially lock up the ability to run the applications. > > I have browsed the support articles and they all seem to apply to the 1.0 > > framework and advise a hotfix to correct the issue. But we are running > the > > 1.1 Framework. > > > > The articles suggest changing the timing of the responseDeadlockInterval > > setting, but don't say whether to increase it or decrease it. > > So which is it? > > > > Any help would be greatly appreciated. > > > > > > Event Type: Error > > Event Source: ASP.NET 1.1.4322.0 > > Event Category: None > > Event ID: 1003 > > Date: 8/22/2003 > > Time: 2:53:32 PM > > User: N/A > > Computer: WEBSERVER > > Description: > > aspnet_wp.exe (PID: 3208) was recycled because it was suspected to be in > a > > deadlocked state. It did not send any responses for pending requests in > the > > last 300 seconds. This timeout may be adjusted using the <processModel > > responseDeadlockInterval> setting in machine.config. > > > > -- > > Martin Blackstone > > MVP - Exchange > > > > http://www.swinc.com/resource/exchange.htm > > > > > > http://www.swinc.com/resource/e2kfaq_appxc.htm > > > > > >
OK, so call me dense, but does that mean I should increase the time? We have
it cranked up to 5 minutes now. The problem is that once we get that error, the ASPNET service is hung and I have to issue an IISReset to get it going again. Also, is this a development issue (bad code), or a Windows issue? -- Martin Blackstone MVP - Exchange http://www.swinc.com/resource/exchange.htm http://www.swinc.com/resource/e2kfaq_appxc.htm [quoted text, click to view] "MS News (MS ILM)" <sql_agentman@hotmail.com> wrote in message news:eVurqvbaDHA.1600@TK2MSFTNGP09.phx.gbl... > responseDeadlockInterval: > > Specifies the time interval, in standard process model format (hr:min:sec), > after which the process will be restarted if the following conditions are > met: > a.. There are queued requests. > b.. There has not been a response during this interval. > The default is 3 minutes. > > > > "Martin Blackstone [MVP - Exchange]" <martinb@myrealbox.com> wrote in > message news:eQN8EQYaDHA.2072@TK2MSFTNGP10.phx.gbl... > > We are seeing a lot of errors like the one below which when occur > > essentially lock up the ability to run the applications. > > I have browsed the support articles and they all seem to apply to the 1.0 > > framework and advise a hotfix to correct the issue. But we are running > the > > 1.1 Framework. > > > > The articles suggest changing the timing of the responseDeadlockInterval > > setting, but don't say whether to increase it or decrease it. > > So which is it? > > > > Any help would be greatly appreciated. > > > > > > Event Type: Error > > Event Source: ASP.NET 1.1.4322.0 > > Event Category: None > > Event ID: 1003 > > Date: 8/22/2003 > > Time: 2:53:32 PM > > User: N/A > > Computer: WEBSERVER > > Description: > > aspnet_wp.exe (PID: 3208) was recycled because it was suspected to be in > a > > deadlocked state. It did not send any responses for pending requests in > the > > last 300 seconds. This timeout may be adjusted using the <processModel > > responseDeadlockInterval> setting in machine.config. > > > > -- > > Martin Blackstone > > MVP - Exchange > > > > http://www.swinc.com/resource/exchange.htm > > > > > > http://www.swinc.com/resource/e2kfaq_appxc.htm > > > > > >
This is W2K Server, IIS5. Does this article apply?
-- Martin Blackstone MVP - Exchange http://www.swinc.com/resource/exchange.htm http://www.swinc.com/resource/e2kfaq_appxc.htm [quoted text, click to view] "MS News (MS ILM)" <sql_agentman@hotmail.com> wrote in message news:e33V85baDHA.2932@tk2msftngp13.phx.gbl... > ISAPI and Worker Process Isolation Mode. > This might help, I meant to send with first reply. > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/iisref/htm/ISAPIAndWorkerProcessIsolationMode.asp > > > > > > "MS News (MS ILM)" <sql_agentman@hotmail.com> wrote in message > news:eVurqvbaDHA.1600@TK2MSFTNGP09.phx.gbl... > > responseDeadlockInterval: > > > > Specifies the time interval, in standard process model format > (hr:min:sec), > > after which the process will be restarted if the following conditions are > > met: > > a.. There are queued requests. > > b.. There has not been a response during this interval. > > The default is 3 minutes. > > > > > > > > "Martin Blackstone [MVP - Exchange]" <martinb@myrealbox.com> wrote in > > message news:eQN8EQYaDHA.2072@TK2MSFTNGP10.phx.gbl... > > > We are seeing a lot of errors like the one below which when occur > > > essentially lock up the ability to run the applications. > > > I have browsed the support articles and they all seem to apply to the > 1.0 > > > framework and advise a hotfix to correct the issue. But we are running > > the > > > 1.1 Framework. > > > > > > The articles suggest changing the timing of the > responseDeadlockInterval > > > setting, but don't say whether to increase it or decrease it. > > > So which is it? > > > > > > Any help would be greatly appreciated. > > > > > > > > > Event Type: Error > > > Event Source: ASP.NET 1.1.4322.0 > > > Event Category: None > > > Event ID: 1003 > > > Date: 8/22/2003 > > > Time: 2:53:32 PM > > > User: N/A > > > Computer: WEBSERVER > > > Description: > > > aspnet_wp.exe (PID: 3208) was recycled because it was suspected to be > in > > a > > > deadlocked state. It did not send any responses for pending requests in > > the > > > last 300 seconds. This timeout may be adjusted using the <processModel > > > responseDeadlockInterval> setting in machine.config. > > > > > > -- > > > Martin Blackstone > > > MVP - Exchange > > > > > > http://www.swinc.com/resource/exchange.htm > > > > > > > > > http://www.swinc.com/resource/e2kfaq_appxc.htm > > > > > > > > > > > >
Decrease it, may be you are going the wrong way.
"Martin Blackstone [MVP - Exchange]" <martinb@myrealbox.com> wrote in message news:u9xTCldaDHA.3444@tk2msftngp13.phx.gbl... [quoted text, click to view] > OK, so call me dense, but does that mean I should increase the time? We have > it cranked up to 5 minutes now. > The problem is that once we get that error, the ASPNET service is hung and I > have to issue an IISReset to get it going again. > > Also, is this a development issue (bad code), or a Windows issue? > > -- > Martin Blackstone > MVP - Exchange > > http://www.swinc.com/resource/exchange.htm > > > http://www.swinc.com/resource/e2kfaq_appxc.htm > "MS News (MS ILM)" <sql_agentman@hotmail.com> wrote in message > news:eVurqvbaDHA.1600@TK2MSFTNGP09.phx.gbl... > > responseDeadlockInterval: > > > > Specifies the time interval, in standard process model format > (hr:min:sec), > > after which the process will be restarted if the following conditions are > > met: > > a.. There are queued requests. > > b.. There has not been a response during this interval. > > The default is 3 minutes. > > > > > > > > "Martin Blackstone [MVP - Exchange]" <martinb@myrealbox.com> wrote in > > message news:eQN8EQYaDHA.2072@TK2MSFTNGP10.phx.gbl... > > > We are seeing a lot of errors like the one below which when occur > > > essentially lock up the ability to run the applications. > > > I have browsed the support articles and they all seem to apply to the > 1.0 > > > framework and advise a hotfix to correct the issue. But we are running > > the > > > 1.1 Framework. > > > > > > The articles suggest changing the timing of the > responseDeadlockInterval > > > setting, but don't say whether to increase it or decrease it. > > > So which is it? > > > > > > Any help would be greatly appreciated. > > > > > > > > > Event Type: Error > > > Event Source: ASP.NET 1.1.4322.0 > > > Event Category: None > > > Event ID: 1003 > > > Date: 8/22/2003 > > > Time: 2:53:32 PM > > > User: N/A > > > Computer: WEBSERVER > > > Description: > > > aspnet_wp.exe (PID: 3208) was recycled because it was suspected to be > in > > a > > > deadlocked state. It did not send any responses for pending requests in > > the > > > last 300 seconds. This timeout may be adjusted using the <processModel > > > responseDeadlockInterval> setting in machine.config. > > > > > > -- > > > Martin Blackstone > > > MVP - Exchange > > > > > > http://www.swinc.com/resource/exchange.htm > > > > > > > > > http://www.swinc.com/resource/e2kfaq_appxc.htm > > > > > > > > > > > >
Are you doing something inside ASP.NET code that you expect to be taking a
long time? If this is the case, increasing the responseDeadlockInterval will be the most direct solution, though changing the requests processing architecture so that a client isn't left waiting for > 3 minutes for a response is probably a better option. If you aren't doing anything that should be taking a long time, you probably have a real thread deadlock, and you need to identify it and fix it. The PAP group has produced a great document on ASP.NET debugging [1] to solve problems like this. For deadlocks, you can add a DWORD value called UnderDebugger to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET key, and when this is set to 1, recycling will be disabled, which allows an Attach to Process on aspnet_wp.exe to occur. [1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/DBGrm.asp Nick Wienholt, MVP Maximizing .NET Performance http://www.apress.com/book/bookDisplay.html?bID=217 Sydney Deep .NET User Group www.sdnug.org "Martin Blackstone [MVP - Exchange]" <martinb@myrealbox.com> wrote in message news:eQN8EQYaDHA.2072@TK2MSFTNGP10.phx.gbl... [quoted text, click to view] > We are seeing a lot of errors like the one below which when occur > essentially lock up the ability to run the applications. > I have browsed the support articles and they all seem to apply to the 1.0 > framework and advise a hotfix to correct the issue. But we are running the > 1.1 Framework. > > The articles suggest changing the timing of the responseDeadlockInterval > setting, but don't say whether to increase it or decrease it. > So which is it? > > Any help would be greatly appreciated. > > > Event Type: Error > Event Source: ASP.NET 1.1.4322.0 > Event Category: None > Event ID: 1003 > Date: 8/22/2003 > Time: 2:53:32 PM > User: N/A > Computer: WEBSERVER > Description: > aspnet_wp.exe (PID: 3208) was recycled because it was suspected to be in a > deadlocked state. It did not send any responses for pending requests in the > last 300 seconds. This timeout may be adjusted using the <processModel > responseDeadlockInterval> setting in machine.config. > > -- > Martin Blackstone > MVP - Exchange > > http://www.swinc.com/resource/exchange.htm > > > http://www.swinc.com/resource/e2kfaq_appxc.htm > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |