"The operation has timed-out" happening intermittently

[sandeep]

Hi
I have a .Net 1.1 Web Service "A" calling into another Web Service "B".
Calls from A to B work fine for most of the time but intermittently I get a
"System.Net.WebException" with the message "The operation has timed-out".
There is no log of this request on B's IIS. Normally the calls from A to B
take only about 300 ms to be processed but when the exception occurs it seems
that A waits for about 100 seconds before throwing the WebException. The
Service A is on a Windows 2000 box with IIS 5.1 and the Web Service B is on
Win 2K3 with IIS 6.0.
Any suggestions will be appreciated.

 

[Sundar Narasimman]

Sandeep,

Did you check the following
1. Is the service B doing some operation involving Data Access
2. If so check whether there is any problem with the database interaction
2. Is service B doing some operation consuming resources
3. Whether service B is sporadically unavailable ?
4. Whether service A is not able to make calls to the sevice sporadically ?
5. Just also check whether connectivity between Service A and Service B is
sporadically unavailable ?

 

[sandeep]

Sundar,
Have checked all of the below. Service B when tested using a non
WebService client ( but with the same data as A would call it ) always
responds quickly no matter how many times it is called. There are no network
issues between A and B. The calls from A that fail with the time-out issue do
not show up on Service B's IIS logs at all. So it almost seems like they
never make it out of Service A's machine. One think I failed to mention is
that Service B is set for Integrated Authentication in IIS.