K
Kevin Jackson
We are running our web application on ASP.NET 1.0.3705.288 and we are
receiving the following message about every 6 to 10 minutes....
aspnet_wp.exe (PID: 860) 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.
There seems to be no logical reason for the recycling.
There are no deadlocks on the database
The aspnet_wp.exe process is not taking up more then 30% of the memory on
the server
It happens even when the web server is under light load
We see no possible reason for ASP.NET to deadlock
We do store state in a SQL database called ASPSTATE
The server hums along just fine until all activity in the aspnet_wp.exe
worker process comes to a halt. 180 seconds later (the default) a new
aspnet_wp.exe spins up and all is fine until the next time.
What are some things to look for when this happens?
receiving the following message about every 6 to 10 minutes....
aspnet_wp.exe (PID: 860) 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.
There seems to be no logical reason for the recycling.
There are no deadlocks on the database
The aspnet_wp.exe process is not taking up more then 30% of the memory on
the server
It happens even when the web server is under light load
We see no possible reason for ASP.NET to deadlock
We do store state in a SQL database called ASPSTATE
The server hums along just fine until all activity in the aspnet_wp.exe
worker process comes to a halt. 180 seconds later (the default) a new
aspnet_wp.exe spins up and all is fine until the next time.
What are some things to look for when this happens?