Timeout!!!

Discussion in 'ASP .Net Web Services' started by Vai2000, Mar 10, 2005.

  1. Vai2000

    Vai2000 Guest

    Here's a configuration
    portal Firewall Box1 Box2
    Client WS1 Ws2

    Client calls WS1 which in turns passes that request to WS2. Sporadically we
    get this error thrown to the client from the WS
    "The underlying connection was closed: The request was cancelled."
    I have increased timeout on all the proxies Client and WS1 to 20minutes and
    I am sure this connection was closed before 20 mins elapsed... We are in
    doldrums of how to resolve this. Like I said it happens seldom so can't
    really replicate this situation.
    Do we need to adjust the executionTimeout attribute value of the httpRunTime
    element on the machine.config?

    TIA
    Vai2000, Mar 10, 2005
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Bob Johnson
    Replies:
    0
    Views:
    3,735
    Bob Johnson
    Aug 7, 2003
  2. Do
    Replies:
    2
    Views:
    6,339
  3. Guoqi Zheng
    Replies:
    4
    Views:
    13,009
    Guoqi Zheng
    Jun 3, 2004
  4. Just D

    IIS timeout, IE timeout or what?

    Just D, Jun 21, 2004, in forum: ASP .Net
    Replies:
    2
    Views:
    3,513
    Just D
    Jun 21, 2004
  5. Mark Probert

    Timeout::timeout and Socket timeout

    Mark Probert, Oct 6, 2004, in forum: Ruby
    Replies:
    1
    Views:
    1,262
    Brian Candler
    Oct 6, 2004
Loading...

Share This Page