NET RUNTIME CRASH ON WIN2K, IIS 5.0

[Guest]

I have a problem similar to that described on
http://www.microsoft.com/communitie...&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us

but I would like specific help on how to solve this.

I get these eventlog entries:

Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1003
Date: 22/03/2006
Time: 22:46:39
User: N/A
Computer: <computername>
Description:
aspnet_wp.exe (PID: 10272) was recycled because it was suspected to be in a
deadlocked state. It did not send any responses for pending requests in the
last 180 seconds. This timeout may be adjusted using the <processModel
responseDeadlockInterval> setting in machine.config.

Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1000
Date: 22/03/2006
Time: 21:42:14
User: N/A
Computer: <computername>
Description:
aspnet_wp.exe (PID: 10740) stopped unexpectedly.

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 0
Date: 22/03/2006
Time: 21:42:13
User: N/A
Computer: <computername>
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: .NET Runtime version 1.1.4322.2032- Setup
Error: Failed to load resources from resource file
Please check your Setup.

There are two applications which use ASP.NET on this IIS 5.0 server, and do
not know for certain which of them is causing the errors.

As a very first step I have made the applications isolated instead of medium
pooled.

assistance would be appreciated.

 

[Bruce Barker]

asp.net is multi threaded, and makes callbacks to user code. if two request
threads make a callback (say pageload), and the callbacks don't return
before the deadlock interval, then it assumes you have bad code thats
deadlocked.

if your page requests actually take over 180 seconds (way too long btw) then
you should increase the interval. if single requests don't take 180 seconds,
then your code is probably deadlocking.


deadlock happen when proper seriazation isn't done for a shared resources.
assume you have two shared resources resourceA and rescourceB.

if thread 1 does

lock resourceA
lock resourceB
// code
release resourceB
release resourceA

and thread 2 does

lock resourceB
lock resourceA
// code
release resourceA
release resourceB

they can deadlock if the thread run at the same time, thread1 gets a lock on
resourceA, thread2 gets a lock on resourceB. now thread1 will wait forever
for resourceB because thread 2 has it locked and is waiting for thread1 to
release resourceA.

-- bruce (sqlwork.com)