Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / September 2006

Tip: Looking for answers? Try searching our database.

"The operation has timed-out" happening intermittently

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
sandeep - 27 Sep 2006 00:28 GMT
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 - 29 Sep 2006 08:24 GMT
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 ?
Signature

Thanks & Regards,
Sundar Narasimman

> Hi
>   I have a .Net 1.1 Web Service "A"  calling into another Web Service "B".
[quoted text clipped - 6 lines]
> Win 2K3 with IIS 6.0.
> Any suggestions will be appreciated.
sandeep - 29 Sep 2006 21:27 GMT
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.

> Sandeep,
>
[quoted text clipped - 17 lines]
> > Win 2K3 with IIS 6.0.
> > Any suggestions will be appreciated.

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.