Hi, We are getting a Server Too Busy message during peak times on our forum. After looking in the logs it looks like the error is being caused by a deadlock. Our sites is http://forum.tonyferguson.com/ (See full error message and details from event viewer below.) Do you know what could be causing the deadlock? What load should we expect to be able to handle on a single low-end server? The server is running Windows Server 2003. Our main site runs on the same server in a seperate application pool and it continues to operate while the forum is down. Regards,
Greg Server Error in '/' Application.
Server Too Busy Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Server Too Busy
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
[HttpException (0x80004005): Server Too Busy] System.Web.HttpRuntime.RejectRequestInternal(HttpWorkerRequest wr) +147 |
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300 Appliaction Log: Event Type: Warning
Event Source: W3SVC-WP
Event Category: None
Event ID: 2262
Date: 1/02/2007
Time: 1:13:48 PM
User: N/A
Computer: WIC227DSB
Description:
ISAPI 'c:\windows\microsoft.net\framework\v1.1.4322\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'. System Log: Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 1/02/2007
Time: 12:30:56 PM
User: N/A
Computer: WIC227DSB
Description:
A process serving application pool 'forum.tonyferguson.com' exceeded time limits during shut down. The process id was '3492'.
|