In our web application we are calling different XML Webservices and
make approximately 25 calls every 10 minutes. We use a separate thread
to call a the webservice (Crawler) and populate our cache -- our
application then retrieves the data from the Cache -- the cache is set
to expire in approximately 25 minutes -- but since the Crawler
populates the cache every 10 minutes with the new data -- thus it never
expires.
In above scenario -- our webserver seems to stop responding after some
hours and we noticed that somehow requests to Webservices were piled-up
in IIS resulting in the delay and sometime 'Operation Timed out'.
we get the following error in the Event Viewer:
ISAPI 'C:\Windows\Microsoft.net\Framework\v.1.1.4322\asp net_isapi.dll'
reported itself as
unhealthy for the following reason: 'Deadlock detected'.
We referred to the following article and made appropriate changes in
the machine.config.
Contention, poor performance, and deadlocks when you make Web service
requests from ASP.NET applications
http://support.microsoft.com/?id=821268
However, our server still seem to timeout and waits for some requests
to the webservices to complete resulting in a delay or sometime 'Server
Timedout' errors, however after applying the above changes to
machine.config -- the application seems to recover from the delay after
sometime.
Please help us rectify the problem.
We'll appreciate your early response,
Thanks,
Zubair.NET!