Server Too Busy Error

From time to time I am receiving server too busy errors

<httpRuntime
maxRequestLength="1536"
executionTimeout="60"
appRequestQueueLimit="700"
/
These are my settings in my web.config. Is there anyway to monitor the apprequestqueue live? It seems a little odd that its going over 700. I server about 1.3 million pages per day so it is possible. I thought it would be interesting to keep a closer eye on it.

Is there any downside to upping to to say 1500 for safety?

Thanks
mike123I'd suggest setting up Performance Monitor to log the Queue numbers over a period of time. See if the traffic is hitting the limit based on normal traffic, or if perhaps some event (or specific page) is causing a large jump in queued pages -- which would indicate a problem that needs to be trouble-shooted with the code.

Server too busy error

Hi.
I have an asp.net application running under Windows 2003 Server, IIS 6, for
seven months. Today, suddenly, the application raised an error entitled
"Server too busy". Searching the event logs I found an entry for:
Event ID: 2262
Description: ISAPI
'C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll' reported
itself as unhealthy for the following reason: 'Deadlock detected'.
What kind of deadlock can it be?
I followed the steps from the MS article
http://support.microsoft.com/defaul...kb;en-us;828222 , but it does
not clarified my doubts. I read the other links pointed by the article but
what exactly does the OrphanWorkerProcess parameter do for me?
TIA,
Erik CruzIf you're doing any multithreading, that would be the #1 suspect.
Also, you might check to be sure you're calling Application.Lock() before
setting any application variables and Application.Unlock() afterward.
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"Erik Cruz" <erikacf.spammers.out@.antares.com.br> wrote in message
news:el7tLJWFFHA.1924@.TK2MSFTNGP14.phx.gbl...
> Hi.
> I have an asp.net application running under Windows 2003 Server, IIS 6,
> for seven months. Today, suddenly, the application raised an error
> entitled "Server too busy". Searching the event logs I found an entry for:
> Event ID: 2262
> Description: ISAPI
> 'C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll' reported
> itself as unhealthy for the following reason: 'Deadlock detected'.
> What kind of deadlock can it be?
> I followed the steps from the MS article
> http://support.microsoft.com/defaul...kb;en-us;828222 , but it
> does not clarified my doubts. I read the other links pointed by the
> article but what exactly does the OrphanWorkerProcess parameter do for me?
> TIA,
> Erik Cruz
>
OrphanWorkerProcess tells IIS not to shutdown the worker process. IIS
will leave the process running but won't send the worker process any
more requests to execute. This setting lets the process stay in memory
so you can jump in with tools like a debugger and see where the
deadlock is occuring.
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 18 Feb 2005 00:35:48 -0300, "Erik Cruz"
<erikacf.spammers.out@.antares.com.br> wrote:

>Hi.
>I have an asp.net application running under Windows 2003 Server, IIS 6, for
>seven months. Today, suddenly, the application raised an error entitled
>"Server too busy". Searching the event logs I found an entry for:
>Event ID: 2262
>Description: ISAPI
>'C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll' reported
>itself as unhealthy for the following reason: 'Deadlock detected'.
>What kind of deadlock can it be?
>I followed the steps from the MS article
>http://support.microsoft.com/defaul...kb;en-us;828222 , but it doe
s
>not clarified my doubts. I read the other links pointed by the article but
>what exactly does the OrphanWorkerProcess parameter do for me?
>TIA,
>Erik Cruz
>
Hi Scott.
Thanks for the information.
The article shows how to enable OrphanWorkerProcess. Is it enough to set it
to False in order to disable it? Will the other parameters be reset
automatically or do I need to change the values manually?
TIA,
Erik Cruz
"Scott Allen" <scott@.nospam.odetocode.com> wrote in message
news:u4tb11pugib2otm9jhmb8hf7lfj95k2o56@.
4ax.com...
> OrphanWorkerProcess tells IIS not to shutdown the worker process. IIS
> will leave the process running but won't send the worker process any
> more requests to execute. This setting lets the process stay in memory
> so you can jump in with tools like a debugger and see where the
> deadlock is occuring.
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
> On Fri, 18 Feb 2005 00:35:48 -0300, "Erik Cruz"
> <erikacf.spammers.out@.antares.com.br> wrote:
>
>
Hi Erik:
Yes, if you set to false the other parameters / actions will not be
taken.
Scott
http://www.OdeToCode.com/blogs/scott/
On Sun, 6 Mar 2005 23:51:43 -0300, "Erik Cruz"
<erikacf.spammers.out@.antares.com.br> wrote:

>Hi Scott.
>Thanks for the information.
>The article shows how to enable OrphanWorkerProcess. Is it enough to set it
>to False in order to disable it? Will the other parameters be reset
>automatically or do I need to change the values manually?
>TIA,
>Erik Cruz
>