[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2629
  • Last Modified:

Odd behavior with app pools in Server 2008 R2

Hey everyone,

I have an odd issue going on here on our web server where the application pools seem to just hang and ultimately terminate.  However, even after recycling there are numerous issues and we ultimately have to reboot the server.  On each occurence I see the following errors that log:

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:      
Event ID:      5011
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      
Description:
A process serving application pool 'app' suffered a fatal
communication error with the Windows Process Activation Service. The
process id was '3492'. The data field contains the error number.
---------------------------------------

Which also seems to coincide with the following .NET error:

Log Name:      Application
Source:        Microsoft-Windows-IIS-W3SVC-WP
Date:          
Event ID:      2262
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:    
Description:
ISAPI 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.
-------------------------------------------------

However, after the most recent occurrence things seemed to be working fine for about a day, until I tried to manually recycle the app pools as a test and the same errors began to log.  When recycling though, I noticed that the pools took a LONG time to come down, which is reflected in the logs:

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          
Event ID:      5138
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      
Description:
A worker process '2864' serving application pool 'pool' failed to stop a listener channel for protocol 'http' in the allotted time.  The data field contains the error number.
-----------------------------------------

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          
Event ID:      5013
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      
Description:
A process serving application pool 'pool' exceeded time limits during shut down. The process id was '2864'.
----------------------------------

So is it possible that there is something wrong with the stop / start logic of the app pools, or is there maybe something else behind the scenes?  Just for reference, we are 2008 R2, IIS 7.5, .NET 4.0.30319

Thanks in advance
0
blinkme323
Asked:
blinkme323
1 Solution
 
Miguel OzSoftware EngineerCommented:
Your problem may be that your site is calling a long running Web Service /database operation.
Please check executionTimeout section of the following this link:
http://support.microsoft.com/kb/821268
0
 
blinkme323Author Commented:
It turns out that some database replication software was installed on the DB server.  Once that was uninstalled, everything returned to normal.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now