aspnet_wp.exe Problem

[Guest]

I have performance issues with aspnet_wp.exe. Some time I got the following
errors on the production server and hang-up the server until I killed the
process. Please advice!

aspnet_wp.exe (PID: 3648) stopped unexpectedly.

aspnet_wp.exe (PID: 4136) 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.

aspnet_wp.exe (PID: 1320) was recycled because memory consumption exceeded
the 613 MB (60 percent of available RAM).

 

[Ben Strackany]

Maybe a memory leak or some deadlocking DB/file access issues. Maybe debug
it to see what's happening?

 

[John M Deal]

If you are using Windows 2003 Server you might want to check the
properties page for the IIS6 application pool that your web application
belongs to to see if it has been configured to reset based on a
particular set of memory and/or processing thresholds. This is supposed
to act as a "last chance catch" for runaway systems. You should then
compare the settings there against the processes that are taking place
and the types of objects that you are keeping alive/building at that
time. If it is a configuration thing you can override or turn off these
settings, though it would be better to find out why your application is
going out of control.

By the way it isn't necessarily your application that is causing the
issue. These settings are applied to the application pool as a whole, so
if any application (or all of them together) causes the threshold to be
exceeded then the worker process that hosts them will be reset. Hope
this helps in some way.

Have A Better One!

John M Deal, MCP
Necessity Software

 

[Guest]

Depending on the .NET version you are running, there are patches for ASP.NET
wp deadlocks and recycling issues.
Aleksey Nudelman
http://csharpcomputing.com

 

[Richard Blewett [DevelopMentor]]

I've seen this on a consult when the ASP.NET threads were tied up performing long running tasks and therefore no new requests were being processed. In this case, after an amount of time (configurable via the processModel element in machine.config in IIS5 or via the properties of the application pool in IIS6) ASP.NET decides that the threads must have got deadlocked and so nuked the worker process and started again. We made the pages in question implement IHttpAsyncHandler and used a custom threadpool to free up the ASP.NET threads from the long running tasks IIRC.

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

I have performance issues with aspnet_wp.exe. Some time I got the following
errors on the production server and hang-up the server until I killed the
process. Please advice!

aspnet_wp.exe (PID: 3648) stopped unexpectedly.

aspnet_wp.exe (PID: 4136) 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.

aspnet_wp.exe (PID: 1320) was recycled because memory consumption exceeded
the 613 MB (60 percent of available RAM).

 

[Guest]

Thank you for your comments! I am using Windows 2000 Server, IIS5

 

[Guest]

Thanks! Please, can you tell me where can I find those patches? I installed
SP 1 for .NET Framework 1.1

 

[Guest]

Which setting do I have to change?


<processModel
enable="true"
timeout="Infinite"
idleTimeout="Infinite"
shutdownTimeout="0:00:05"
requestLimit="Infinite"
requestQueueLimit="5000"
restartQueueLimit="10"
memoryLimit="60"
webGarden="false"
cpuMask="0xffffffff"
userName="grandaerie\asp"
password="#*j8Ql1@"
logLevel="Errors"
clientConnectedCheck="0:00:05"
comAuthenticationLevel="Connect"
comImpersonationLevel="Impersonate"
responseDeadlockInterval="00:03:00"
maxWorkerThreads="20"
maxIoThreads="20"
/>

Thanks

 

[Richard Blewett [DevelopMentor]]

You want to look at the memoryLimit (looking at your original post) and your responseDeadllockInterval

However, you also want to work out why you are hitting these limits - changing them may simply mask a structural problem in your application

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

Which setting do I have to change?


<processModel
enable="true"
timeout="Infinite"
idleTimeout="Infinite"
shutdownTimeout="0:00:05"
requestLimit="Infinite"
requestQueueLimit="5000"
restartQueueLimit="10"
memoryLimit="60"
webGarden="false"
cpuMask="0xffffffff"
userName="grandaerie\asp"
password="#*j8Ql1@"
logLevel="Errors"
clientConnectedCheck="0:00:05"
comAuthenticationLevel="Connect"
comImpersonationLevel="Impersonate"
responseDeadlockInterval="00:03:00"
maxWorkerThreads="20"
maxIoThreads="20"
/>

Thanks