Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Services > Can't diagnose time-out errors

Reply
Thread Tools

Can't diagnose time-out errors

 
 
Brad Wood
Guest
Posts: n/a
 
      12-02-2005
<environment>
Consuming a web service from a VS2005 beta 2 test harness on WinXP. Web
service built with VS2003 running on my machine with IIS 5X set to use
ASP.NET 1.1
</environment>

I have a web service wherein I make http calls out using the
HttpWebResponse.GetResponse method. This works fine when making these
calls normally (no threading).

I created a winforms test app and tested using the same code to make
http calls in multiple threads and tested numerous threads (50 threads
would consistently work fine).

When I incorporate that same thread code back into my web service, I get
error "System.Net.WebException: The operation has timed out."

I've:
- Ensured I'm closing all necessary objects in my http code.
- Tried making adjustments to the httpRuntime config element.
- Increased the maxconnection amount in the connectionManagement config
element.
- Set the Timeout property of my HttpWebResponse object to Timeout.Infinite.
- Set the KeepAlive property of my HttpWebResponse object to false.

I'm hoping someone can suggest something else to look at...
 
Reply With Quote
 
 
 
 
Brad Wood
Guest
Posts: n/a
 
      12-02-2005
Sorry, should have checked this before even researching and posting:
all of the HttpWebResponse.GetResponse calls are returning fine in my
web service - it's just that my test app back in VS2005 times out first.
So it seems to be an issue unrelated to my web service...?

Brad Wood wrote:
> <environment>
> Consuming a web service from a VS2005 beta 2 test harness on WinXP. Web
> service built with VS2003 running on my machine with IIS 5X set to use
> ASP.NET 1.1
> </environment>
>
> I have a web service wherein I make http calls out using the
> HttpWebResponse.GetResponse method. This works fine when making these
> calls normally (no threading).
>
> I created a winforms test app and tested using the same code to make
> http calls in multiple threads and tested numerous threads (50 threads
> would consistently work fine).
>
> When I incorporate that same thread code back into my web service, I get
> error "System.Net.WebException: The operation has timed out."
>
> I've:
> - Ensured I'm closing all necessary objects in my http code.
> - Tried making adjustments to the httpRuntime config element.
> - Increased the maxconnection amount in the connectionManagement config
> element.
> - Set the Timeout property of my HttpWebResponse object to
> Timeout.Infinite.
> - Set the KeepAlive property of my HttpWebResponse object to false.
>
> I'm hoping someone can suggest something else to look at...

 
Reply With Quote
 
 
 
 
Brad Wood
Guest
Posts: n/a
 
      12-02-2005
Sorry, I shouldn't have posted; it's merely a matter of changing the
Timeout property on the auto-generated web service proxy object used by
my test code.

Brad Wood wrote:
> Sorry, should have checked this before even researching and posting: all
> of the HttpWebResponse.GetResponse calls are returning fine in my web
> service - it's just that my test app back in VS2005 times out first.
> So it seems to be an issue unrelated to my web service...?

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Pls Help Diagnose Router Errors mike Cisco 3 09-25-2006 10:37 PM
How do I diagnose an error? =?Utf-8?B?S2V2aW4gQnVydG9u?= ASP .Net 2 12-10-2004 03:29 PM
ASP.NET HANG NO RESPONSE:HOW TO DIAGNOSE THE PROBLEM ? =?Utf-8?B?Y2Flc2FyY2hlbg==?= ASP .Net 1 09-30-2004 05:23 PM
How to diagnose connection pool exhaustion? Simon Devlin ASP .Net 0 01-21-2004 09:35 PM
Errors, errors, errors Mark Goldin ASP .Net 2 01-17-2004 08:05 PM



Advertisments