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?. I think it's too low for the
simultaneous http connections I have (about 100 connections), maybe the
users are mostly getting static content. Anyway, I don't have any problems
in the last 48 hours.

Best regards,
Roberto

"Anthony Jones" <Ant@y...> wrote in message
news:OqpF1sqBIHA.3848@T......
>
> "Roberto T." <r_t@n...> wrote in message
> news:eEju5amBIHA.5160@T......
> > I have solved the problem migrating a web service to another server, and
I
> > have no timeouts in the last 24 hours.
> > So the problem was not related to serverxmlhttp, but with IIS.
> >
>
> Is the new web server a faster server with more processors/memory than the
> original?
>
> > I am not abandoning the sessions created by serverXMLHTTP, will apply it
> to
> > al my web services.
>
> If you are implementing significant web services in ASP you should
consider
> placing those services in a separate application and turn of session state
> for that application.
>
> Otherwise yes you should abandon the session after each request.
>
>
> -- 
> Anthony Jones - MVP ASP/ASP.NET
>
>