"Roberto T." <r_t@n...> wrote in message
news:uVgdY0OBIHA.4956@T......
> I have a server (W2K SP4, and XML3 SP9) with about 100 simultaneous users,
> that requests information to varius web services (local and remote).
> It has been working fine for years, but in the last months I get frequent
> timeout errors. The ASP requested stalls, and after the configured script
> timeout it crashes.
>
> I have debuged my pages and found that it can crash in different places
> using serverxmlhttp object, I have found a frequent timeout loading an ASP
> page that returns a static XSLT only changing the sort attribute, setting
it
> to the received parameter if any. I doesn't connect to any external
source.
>
> This is a sample of my http calls:
> set objHTTP= CreateObject("Msxml2.serverXMLHTTP")
> objHTTP.Open "POST", "http://local.ws/bin/getXslt.asp", false
> objHTTP.Send  <<<<< I get here the timeout
>
> Could it be a problem with ServerXMLHTTP, DOM, IIS? 100 simultaneous
> connections is too much for one server (2GB RAM, core duo 1.6GHz)? Could
the
> different serverxmlhttp requests block each other?
>

Yes using ServerXMLHTTP in ASP to request other ASP pages on the same server
can starve ASP of threads because threads a blocked waiting for completion
of other ASP threads.  In a worst case scenario the whole thing can lock up.

Also if Session State is enabled are you abandoning the sessions created by
the requests generated by the ServerXMLHTTP requests.


-- 
Anthony Jones - MVP ASP/ASP.NET