Framework Corruption

[Blink]

We finished a project last week, and deployed it on Thursday last. It's been
running all weekend with no problem, then suddenly this morning ASP.NET
started generating deadlock errors ("aspnet_wp.exe (PID: 1836) 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."), and no request
could be made to our application.

We huffed and puffed for an hour or two attempting to fix it, but to no
avail. Eventually we decided to reinstall the .NET Framework, and everything
was magically fine again. Does anyone know why this would have happened?
What could happen to a Framework installation to make it become corrupt, or
suddenly not work? We have a fair idea it wasn't our application that caused
it, as no other application would run either.

 

[Jacky Kwok]

We finished a project last week, and deployed it on Thursday last. It's been
running all weekend with no problem, then suddenly this morning ASP.NET
started generating deadlock errors ("aspnet_wp.exe (PID: 1836) 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."), and no request
could be made to our application.

We huffed and puffed for an hour or two attempting to fix it, but to no
avail. Eventually we decided to reinstall the .NET Framework, and everything
was magically fine again. Does anyone know why this would have happened?
What could happen to a Framework installation to make it become corrupt, or
suddenly not work? We have a fair idea it wasn't our application that caused
it, as no other application would run either.

It will happen when the web request has large size upload data, e.g.
upload file from web browser.

You may need to change the setting in global "machine.config"
"processModel" tag "responseDeadlockInterval" value.

refer
"http://www.websupergoo.com/helpupload50/2-tech_notes/3-web.config.htm".