Today we are receiving quite a few exceptions in IIS. We've made no changes to the website or IIS settings. I've verified with all of my team members to ensure this was the case. We have ASP.NET Health Monitoring enabled and receive the "not so pleasant" exception:
The following exception has been generated from https://unitedoneresources.com/res/: ** Application Information ** --------------- Application domain: /LM/W3SVC/2/ROOT/res-1-129573343750 Trust level: Full Application Virtual Path: /res Application Path: C:\inetpub\wwwroot\unitedoneresources.com\res\ Machine name: NEPA-WEB01 ** Events ** --------------- Event code: 3001 Event message: The request has been aborted. Event time: 8/9/2011 2:56:27 PM Event time (UTC): 8/9/2011 6:56:27 PM Event ID: 7583c8abc19e4e72a0a804fe97f01605 Event sequence: 319 Event occurrence: 1 Event detail code: 0 Process information: Process ID: 3328 Process name: w3wp.exe Account name: IIS APPPOOL\unitedoneresources.com Exception information: Exception type: System.Web.HttpException Exception message: Request timed out. Request information: Request URL: https://unitedoneresources.com:443/res/step8 Request path: /res/step8 User host address: 22.214.171.124 User: firstname.lastname@example.org Is authenticated: True Authentication Type: Forms Thread account name: server\administrator Thread information: Thread ID: 12 Thread account name: server\administrator Is impersonating: False Stack trace: ---------------
If I review the HTTP logs, I notice entries like the following:
2011-08-09 18:28:25 126.96.36.199 37317 172.16.1.80 443 HTTP/1.1 POST /res/step8 - 2 Timer_EntityBody unitedoneresources.com 2011-08-09 18:19:52 188.8.131.52 58599 172.16.1.80 443 HTTP/1.1 POST /res/step3 - 2 Connection_Abandoned_By_ReqQueue unitedoneresources.com
I noticed that after a server reboot, the first entry the third in the log. We tried restarting the server hoping that would solve a few things, but it has not.
After searching online for
Connection_Abandoned_By_ReqQueue, I have been unsuccessful at determining the cause. For
Timer_EntityBody, I see individuals and sites (such as MSDN) suggesting to increase the minimum filebytes per second. However, if it throws this on the third request when it's been working all along, I highly doubt that is the case.
Connection_Abandoned_By_ReqQueue, it seems like many suggest it has to do with an HttpModule or dll not being compatible with IIS7. Again, that doesn't make sense as we haven't updated anything and it's been the same stuff for a year now.
Any help that can be provided is greatly appreciated.