"Roberto T." <r_t@n...> wrote in message
news:eZgUEvyBIHA.4836@T......
> The new server has the same hardware configuration, but less usage.
> I have disabled session state for some services and abandon session in
> others that share the site/virtualdir with other tipe of application.
>
> In performance monitor, in Active Server Pages Object, in the worst cases
I
> see about 10 requests executing and about 5 queued. Don't know why I have
> requests queued if I haven't reached ASPProcessorThreadMax, could it be
ASP
> waiting for ServerXMLHTTP reqeuests?.

There only two reasons I know of for ASP to queue a request when there are
available worker threads.  If a requests arrives for a specific session
whilst a previous request for a specific session is still in progress it has
to be queue until the previous request is complete.  This typically happens
when using frames and the browser happens to make simultaneous requests for
ASPs from the server.

The other reason is due to COM objects being stored in the session.  In this
case a session becomes affiliated with a specific worker thread and will
only run in that thread.  If that thread is currently processing another
request when a request for the session arrives it needs to be queued until
that specific worker thread is available.

Neither of these would seem to causesd by ServerXMLHTTP requests to the same
server.

How busy is the server when processing the 10 requests?

-- 
Anthony Jones - MVP ASP/ASP.NET