"The operation has timed-out." exception on WinXP

Discussion in 'ASP .Net Web Services' started by Joel Zhou, Jul 17, 2003.

  1. Joel Zhou

    Joel Zhou Guest

    Our web clients makes synchronous web method calls to a
    web service on a XP workstation, running .Net 1.1.4322.

    When there are already 10 connections to the IIS, the
    client gets "The request failed with HTTP status 403:
    Access Forbidden." when calling the web service. This is
    expected behavior documented by MSDN. However, my problem
    is if the client (same thread) tries to make the call
    again after the total connection < 10, it will get "The
    operation has timed-out." exception first, and then if the
    client makes the same call again, it will work.

    If the IIS connection stays at 10, the client will get
    those two exceptions one after another. I am expecting the
    client to always get the "..Access Forbidden" exception.

    It seems that after the "...403: Access Forbidden" error,
    the client will always get a "The operation has timed-
    out." before it will work again. I set the client side
    timeout to 30 seconds. The timeout exception happens about
    90 seconds after making the call.

    I am trying to figure out how to avoid the timeout
    exception. Any suggestions?

    The exception call stack is below:
    Error: System.Net.WebException: The operation has timed-
    out.
    at System.Net.HttpWebRequest.GetRequestStream()
    at
    System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    (String methodN
    ame, Object[] parameters)
    at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    methodName, Object[] p
    arameters) in
    d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    :line 3
    Joel Zhou, Jul 17, 2003
    #1
    1. Advertising

  2. Joel Zhou

    Joel Zhou Guest

    Hi Yanhong,

    Thank you for the reply. I did not explicitly open any handle so I am not
    sure if I what I need to close.

    In my web proxy class, I created a new Invoke method to replace the base
    class's Invoke method. In my Invoke method, I call the base class's Invoke,
    and added retry if base class's Invoke throws exception. So when IIS stays
    busy with 10 connections, my Invoke will automatically retry - sleep -
    retry - sleep ... for up to MaxRetry.

    // Replace the base class's Invoke.
    protected new object[] Invoke(string methodName, object[] parameters)
    {
    object[] results = null;
    int nRetries = 0;
    do
    {
    try
    {
    results = base.Invoke(methodName, parameters);
    // if we do not have an exception, we will exit the
    while loop now.
    break;
    }
    catch(System.Net.WebException webExp)
    {
    // On WinXP, this could be "The request failed with HTTP
    status 403: Access Forbidden"
    // This also could be ""The operation has timed-out."
    // we need to retry in both cases
    if (nRetries==MaxRetry)
    {
    throw webExp;
    }
    else
    {
    // sleep sometime before retrying
    System.Threading.Thread.Sleep(RetryInterval);
    }
    }
    nRetries++;
    }while(this.EnableRetry==true);

    return results;
    }


    Thanks
    Joel Zhou



    "Yan-Hong Huang[MSFT]" <> wrote in message
    news:...
    > Hello Joel,
    >
    > I can't tell exactly where the problem exists now. Have you confirmed that

    you have closed all the handles, such as stream
    > handles, and etc.
    >
    > Thanks.
    >
    > Best regards,
    > Yanhong Huang
    > Microsoft Online Partner Support
    >
    > Get Secure! - www.microsoft.com/security
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    >
    > --------------------
    > !Content-Class: urn:content-classes:message
    > !From: "Joel Zhou" <>
    > !Sender: "Joel Zhou" <>
    > !Subject: "The operation has timed-out." exception on WinXP
    > !Date: Wed, 16 Jul 2003 16:03:59 -0700
    > !Lines: 39
    > !Message-ID: <05e601c34bee$8a519d50$>
    > !MIME-Version: 1.0
    > !Content-Type: text/plain;
    > ! charset="iso-8859-1"
    > !Content-Transfer-Encoding: 7bit
    > !X-Newsreader: Microsoft CDO for Windows 2000
    > !X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    > !Thread-Index: AcNL7opR4m2aDJgCSfSToDfa2GQ+3A==
    > !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !Path: cpmsftngxa06.phx.gbl
    > !Xref: cpmsftngxa06.phx.gbl

    microsoft.public.dotnet.framework.aspnet.webservices:18319
    > !NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    > !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !
    > !Our web clients makes synchronous web method calls to a
    > !web service on a XP workstation, running .Net 1.1.4322.
    > !
    > !When there are already 10 connections to the IIS, the
    > !client gets "The request failed with HTTP status 403:
    > !Access Forbidden." when calling the web service. This is
    > !expected behavior documented by MSDN. However, my problem
    > !is if the client (same thread) tries to make the call
    > !again after the total connection < 10, it will get "The
    > !operation has timed-out." exception first, and then if the
    > !client makes the same call again, it will work.
    > !
    > !If the IIS connection stays at 10, the client will get
    > !those two exceptions one after another. I am expecting the
    > !client to always get the "..Access Forbidden" exception.
    > !
    > !It seems that after the "...403: Access Forbidden" error,
    > !the client will always get a "The operation has timed-
    > !out." before it will work again. I set the client side
    > !timeout to 30 seconds. The timeout exception happens about
    > !90 seconds after making the call.
    > !
    > !I am trying to figure out how to avoid the timeout
    > !exception. Any suggestions?
    > !
    > !The exception call stack is below:
    > !Error: System.Net.WebException: The operation has timed-
    > !out.
    > ! at System.Net.HttpWebRequest.GetRequestStream()
    > ! at
    > !System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    > !(String methodN
    > !ame, Object[] parameters)
    > ! at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    > !methodName, Object[] p
    > !arameters) in
    > !d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    > !:line 3
    > !
    > !
    >
    >
    Joel Zhou, Jul 18, 2003
    #2
    1. Advertising

  3. Hello Joel,

    I did reproduce it on my side. The next exception (timed-out) happens after each 403 error. I will dig into it and reply you with
    more information on it.

    Thanks very much.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !Reply-To: "Joel Zhou" <>
    !From: "Joel Zhou" <>
    !References: <05e601c34bee$8a519d50$> <>
    <#> <>
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !Date: Wed, 23 Jul 2003 14:06:32 -0500
    !Lines: 217
    !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !Message-ID: <#>
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18428
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !
    !Hi Yanhong,
    !
    !I tried to simplify the problem by creating a web service, and then added
    !web reference of this web service in a C# console test client. I did not put
    !my custom Invoke in the proxy this time. I kept the IIS busy by launching a
    !web client and kept the current connection at 10 (maximum allowed by WinXP).
    !When I launch the test client, I got the following exception one after
    !another:
    !The request failed with HTTP status 403: Access Forbidden.
    !The operation has timed-out.
    !The request failed with HTTP status 403: Access Forbidden.
    !The operation has timed-out.
    !...
    !
    !In the test client, the code is simply calling the same method on the web
    !service in a while loop.
    !
    !localhost.Service1 webProxy = new localhost.Service1();
    !while (true)
    !{
    ! try
    ! {
    ! string result = webProxy.Sleep(1000);
    ! Console.WriteLine("Done. Result = {0}", result);
    ! }
    ! catch(Exception e)
    ! {
    ! Console.WriteLine("Failed. Exception={0}", e.Message);
    ! }
    !}
    !return;
    !
    !Thanks for your help,
    !Joel
    !
    !
    !
    !"Yan-Hong Huang[MSFT]" <> wrote in message
    !news:...
    !> Hello Joel,
    !>
    !> Then if you remove this part of code, did you meet this problem? We need
    !to isolate the problem before digging into it. :)
    !> Thanks very much.
    !>
    !> Best regards,
    !> Yanhong Huang
    !> Microsoft Online Partner Support
    !>
    !> Get Secure! - www.microsoft.com/security
    !> This posting is provided "AS IS" with no warranties, and confers no
    !rights.
    !>
    !> --------------------
    !> !Reply-To: "Joel Zhou" <>
    !> !From: "Joel Zhou" <>
    !> !References: <05e601c34bee$8a519d50$>
    !<>
    !> !Subject: Re: "The operation has timed-out." exception on WinXP
    !> !Date: Fri, 18 Jul 2003 11:32:18 -0500
    !> !Lines: 137
    !> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !> !Message-ID: <#>
    !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !> !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    !> !Xref: cpmsftngxa06.phx.gbl
    !microsoft.public.dotnet.framework.aspnet.webservices:18362
    !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !> !
    !> !Hi Yanhong,
    !> !
    !> !Thank you for the reply. I did not explicitly open any handle so I am not
    !> !sure if I what I need to close.
    !> !
    !> !In my web proxy class, I created a new Invoke method to replace the base
    !> !class's Invoke method. In my Invoke method, I call the base class's
    !Invoke,
    !> !and added retry if base class's Invoke throws exception. So when IIS
    !stays
    !> !busy with 10 connections, my Invoke will automatically retry - sleep -
    !> !retry - sleep ... for up to MaxRetry.
    !> !
    !> !// Replace the base class's Invoke.
    !> !protected new object[] Invoke(string methodName, object[] parameters)
    !> ! {
    !> ! object[] results = null;
    !> ! int nRetries = 0;
    !> ! do
    !> ! {
    !> ! try
    !> ! {
    !> ! results = base.Invoke(methodName, parameters);
    !> ! // if we do not have an exception, we will exit the
    !> !while loop now.
    !> ! break;
    !> ! }
    !> ! catch(System.Net.WebException webExp)
    !> ! {
    !> ! // On WinXP, this could be "The request failed with
    !HTTP
    !> !status 403: Access Forbidden"
    !> ! // This also could be ""The operation has timed-out."
    !> ! // we need to retry in both cases
    !> ! if (nRetries==MaxRetry)
    !> ! {
    !> ! throw webExp;
    !> ! }
    !> ! else
    !> ! {
    !> ! // sleep sometime before retrying
    !> ! System.Threading.Thread.Sleep(RetryInterval);
    !> ! }
    !> ! }
    !> ! nRetries++;
    !> ! }while(this.EnableRetry==true);
    !> !
    !> ! return results;
    !> ! }
    !> !
    !> !
    !> !Thanks
    !> !Joel Zhou
    !> !
    !> !
    !> !
    !> !"Yan-Hong Huang[MSFT]" <> wrote in message
    !> !news:...
    !> !> Hello Joel,
    !> !>
    !> !> I can't tell exactly where the problem exists now. Have you confirmed
    !that
    !> !you have closed all the handles, such as stream
    !> !> handles, and etc.
    !> !>
    !> !> Thanks.
    !> !>
    !> !> Best regards,
    !> !> Yanhong Huang
    !> !> Microsoft Online Partner Support
    !> !>
    !> !> Get Secure! - www.microsoft.com/security
    !> !> This posting is provided "AS IS" with no warranties, and confers no
    !> !rights.
    !> !>
    !> !> --------------------
    !> !> !Content-Class: urn:content-classes:message
    !> !> !From: "Joel Zhou" <>
    !> !> !Sender: "Joel Zhou" <>
    !> !> !Subject: "The operation has timed-out." exception on WinXP
    !> !> !Date: Wed, 16 Jul 2003 16:03:59 -0700
    !> !> !Lines: 39
    !> !> !Message-ID: <05e601c34bee$8a519d50$>
    !> !> !MIME-Version: 1.0
    !> !> !Content-Type: text/plain;
    !> !> ! charset="iso-8859-1"
    !> !> !Content-Transfer-Encoding: 7bit
    !> !> !X-Newsreader: Microsoft CDO for Windows 2000
    !> !> !X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    !> !> !Thread-Index: AcNL7opR4m2aDJgCSfSToDfa2GQ+3A==
    !> !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !> !> !Path: cpmsftngxa06.phx.gbl
    !> !> !Xref: cpmsftngxa06.phx.gbl
    !> !microsoft.public.dotnet.framework.aspnet.webservices:18319
    !> !> !NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    !> !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !> !> !
    !> !> !Our web clients makes synchronous web method calls to a
    !> !> !web service on a XP workstation, running .Net 1.1.4322.
    !> !> !
    !> !> !When there are already 10 connections to the IIS, the
    !> !> !client gets "The request failed with HTTP status 403:
    !> !> !Access Forbidden." when calling the web service. This is
    !> !> !expected behavior documented by MSDN. However, my problem
    !> !> !is if the client (same thread) tries to make the call
    !> !> !again after the total connection < 10, it will get "The
    !> !> !operation has timed-out." exception first, and then if the
    !> !> !client makes the same call again, it will work.
    !> !> !
    !> !> !If the IIS connection stays at 10, the client will get
    !> !> !those two exceptions one after another. I am expecting the
    !> !> !client to always get the "..Access Forbidden" exception.
    !> !> !
    !> !> !It seems that after the "...403: Access Forbidden" error,
    !> !> !the client will always get a "The operation has timed-
    !> !> !out." before it will work again. I set the client side
    !> !> !timeout to 30 seconds. The timeout exception happens about
    !> !> !90 seconds after making the call.
    !> !> !
    !> !> !I am trying to figure out how to avoid the timeout
    !> !> !exception. Any suggestions?
    !> !> !
    !> !> !The exception call stack is below:
    !> !> !Error: System.Net.WebException: The operation has timed-
    !> !> !out.
    !> !> ! at System.Net.HttpWebRequest.GetRequestStream()
    !> !> ! at
    !> !> !System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    !> !> !(String methodN
    !> !> !ame, Object[] parameters)
    !> !> ! at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    !> !> !methodName, Object[] p
    !> !> !arameters) in
    !> !> !d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    !> !> !:line 3
    !> !> !
    !> !> !
    !> !>
    !> !>
    !> !
    !> !
    !> !
    !>
    !>
    !
    !
    !
    Yan-Hong Huang[MSFT], Jul 24, 2003
    #3
  4. Hi Joel,

    We are still performing research on it. It may need some more time. Sorry for any inconvenience.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !X-Tomcat-ID: 243274584
    !References: <05e601c34bee$8a519d50$> <>
    <#> <> <#sD2G3UUDHA.2368
    @TK2MSFTNGP09.phx.gbl>
    !MIME-Version: 1.0
    !Content-Type: text/plain
    !Content-Transfer-Encoding: 7bit
    !From: (Yan-Hong Huang[MSFT])
    !Organization: Microsoft
    !Date: Thu, 24 Jul 2003 09:54:36 GMT
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !Message-ID: <>
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !Lines: 232
    !Path: cpmsftngxa06.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18442
    !NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
    !
    !Hello Joel,
    !
    !I did reproduce it on my side. The next exception (timed-out) happens after each 403 error. I will dig into it and reply you with
    !more information on it.
    !
    !Thanks very much.
    !
    !Best regards,
    !Yanhong Huang
    !Microsoft Online Partner Support
    !
    !Get Secure! - www.microsoft.com/security
    !This posting is provided "AS IS" with no warranties, and confers no rights.
    !
    !--------------------
    !!Reply-To: "Joel Zhou" <>
    !!From: "Joel Zhou" <>
    !!References: <05e601c34bee$8a519d50$> <>
    !<#> <>
    !!Subject: Re: "The operation has timed-out." exception on WinXP
    !!Date: Wed, 23 Jul 2003 14:06:32 -0500
    !!Lines: 217
    !!X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !!Message-ID: <#>
    !!Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !!NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !!Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
    !!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18428
    !!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !!
    !!Hi Yanhong,
    !!
    !!I tried to simplify the problem by creating a web service, and then added
    !!web reference of this web service in a C# console test client. I did not put
    !!my custom Invoke in the proxy this time. I kept the IIS busy by launching a
    !!web client and kept the current connection at 10 (maximum allowed by WinXP).
    !!When I launch the test client, I got the following exception one after
    !!another:
    !!The request failed with HTTP status 403: Access Forbidden.
    !!The operation has timed-out.
    !!The request failed with HTTP status 403: Access Forbidden.
    !!The operation has timed-out.
    !!...
    !!
    !!In the test client, the code is simply calling the same method on the web
    !!service in a while loop.
    !!
    !!localhost.Service1 webProxy = new localhost.Service1();
    !!while (true)
    !!{
    !! try
    !! {
    !! string result = webProxy.Sleep(1000);
    !! Console.WriteLine("Done. Result = {0}", result);
    !! }
    !! catch(Exception e)
    !! {
    !! Console.WriteLine("Failed. Exception={0}", e.Message);
    !! }
    !!}
    !!return;
    !!
    !!Thanks for your help,
    !!Joel
    !!
    !!
    !!
    !!"Yan-Hong Huang[MSFT]" <> wrote in message
    !!news:...
    !!> Hello Joel,
    !!>
    !!> Then if you remove this part of code, did you meet this problem? We need
    !!to isolate the problem before digging into it. :)
    !!> Thanks very much.
    !!>
    !!> Best regards,
    !!> Yanhong Huang
    !!> Microsoft Online Partner Support
    !!>
    !!> Get Secure! - www.microsoft.com/security
    !!> This posting is provided "AS IS" with no warranties, and confers no
    !!rights.
    !!>
    !!> --------------------
    !!> !Reply-To: "Joel Zhou" <>
    !!> !From: "Joel Zhou" <>
    !!> !References: <05e601c34bee$8a519d50$>
    !!<>
    !!> !Subject: Re: "The operation has timed-out." exception on WinXP
    !!> !Date: Fri, 18 Jul 2003 11:32:18 -0500
    !!> !Lines: 137
    !!> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !!> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !!> !Message-ID: <#>
    !!> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !!> !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !!> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    !!> !Xref: cpmsftngxa06.phx.gbl
    !!microsoft.public.dotnet.framework.aspnet.webservices:18362
    !!> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !!> !
    !!> !Hi Yanhong,
    !!> !
    !!> !Thank you for the reply. I did not explicitly open any handle so I am not
    !!> !sure if I what I need to close.
    !!> !
    !!> !In my web proxy class, I created a new Invoke method to replace the base
    !!> !class's Invoke method. In my Invoke method, I call the base class's
    !!Invoke,
    !!> !and added retry if base class's Invoke throws exception. So when IIS
    !!stays
    !!> !busy with 10 connections, my Invoke will automatically retry - sleep -
    !!> !retry - sleep ... for up to MaxRetry.
    !!> !
    !!> !// Replace the base class's Invoke.
    !!> !protected new object[] Invoke(string methodName, object[] parameters)
    !!> ! {
    !!> ! object[] results = null;
    !!> ! int nRetries = 0;
    !!> ! do
    !!> ! {
    !!> ! try
    !!> ! {
    !!> ! results = base.Invoke(methodName, parameters);
    !!> ! // if we do not have an exception, we will exit the
    !!> !while loop now.
    !!> ! break;
    !!> ! }
    !!> ! catch(System.Net.WebException webExp)
    !!> ! {
    !!> ! // On WinXP, this could be "The request failed with
    !!HTTP
    !!> !status 403: Access Forbidden"
    !!> ! // This also could be ""The operation has timed-out."
    !!> ! // we need to retry in both cases
    !!> ! if (nRetries==MaxRetry)
    !!> ! {
    !!> ! throw webExp;
    !!> ! }
    !!> ! else
    !!> ! {
    !!> ! // sleep sometime before retrying
    !!> ! System.Threading.Thread.Sleep(RetryInterval);
    !!> ! }
    !!> ! }
    !!> ! nRetries++;
    !!> ! }while(this.EnableRetry==true);
    !!> !
    !!> ! return results;
    !!> ! }
    !!> !
    !!> !
    !!> !Thanks
    !!> !Joel Zhou
    !!> !
    !!> !
    !!> !
    !!> !"Yan-Hong Huang[MSFT]" <> wrote in message
    !!> !news:...
    !!> !> Hello Joel,
    !!> !>
    !!> !> I can't tell exactly where the problem exists now. Have you confirmed
    !!that
    !!> !you have closed all the handles, such as stream
    !!> !> handles, and etc.
    !!> !>
    !!> !> Thanks.
    !!> !>
    !!> !> Best regards,
    !!> !> Yanhong Huang
    !!> !> Microsoft Online Partner Support
    !!> !>
    !!> !> Get Secure! - www.microsoft.com/security
    !!> !> This posting is provided "AS IS" with no warranties, and confers no
    !!> !rights.
    !!> !>
    !!> !> --------------------
    !!> !> !Content-Class: urn:content-classes:message
    !!> !> !From: "Joel Zhou" <>
    !!> !> !Sender: "Joel Zhou" <>
    !!> !> !Subject: "The operation has timed-out." exception on WinXP
    !!> !> !Date: Wed, 16 Jul 2003 16:03:59 -0700
    !!> !> !Lines: 39
    !!> !> !Message-ID: <05e601c34bee$8a519d50$>
    !!> !> !MIME-Version: 1.0
    !!> !> !Content-Type: text/plain;
    !!> !> ! charset="iso-8859-1"
    !!> !> !Content-Transfer-Encoding: 7bit
    !!> !> !X-Newsreader: Microsoft CDO for Windows 2000
    !!> !> !X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    !!> !> !Thread-Index: AcNL7opR4m2aDJgCSfSToDfa2GQ+3A==
    !!> !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !!> !> !Path: cpmsftngxa06.phx.gbl
    !!> !> !Xref: cpmsftngxa06.phx.gbl
    !!> !microsoft.public.dotnet.framework.aspnet.webservices:18319
    !!> !> !NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    !!> !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !!> !> !
    !!> !> !Our web clients makes synchronous web method calls to a
    !!> !> !web service on a XP workstation, running .Net 1.1.4322.
    !!> !> !
    !!> !> !When there are already 10 connections to the IIS, the
    !!> !> !client gets "The request failed with HTTP status 403:
    !!> !> !Access Forbidden." when calling the web service. This is
    !!> !> !expected behavior documented by MSDN. However, my problem
    !!> !> !is if the client (same thread) tries to make the call
    !!> !> !again after the total connection < 10, it will get "The
    !!> !> !operation has timed-out." exception first, and then if the
    !!> !> !client makes the same call again, it will work.
    !!> !> !
    !!> !> !If the IIS connection stays at 10, the client will get
    !!> !> !those two exceptions one after another. I am expecting the
    !!> !> !client to always get the "..Access Forbidden" exception.
    !!> !> !
    !!> !> !It seems that after the "...403: Access Forbidden" error,
    !!> !> !the client will always get a "The operation has timed-
    !!> !> !out." before it will work again. I set the client side
    !!> !> !timeout to 30 seconds. The timeout exception happens about
    !!> !> !90 seconds after making the call.
    !!> !> !
    !!> !> !I am trying to figure out how to avoid the timeout
    !!> !> !exception. Any suggestions?
    !!> !> !
    !!> !> !The exception call stack is below:
    !!> !> !Error: System.Net.WebException: The operation has timed-
    !!> !> !out.
    !!> !> ! at System.Net.HttpWebRequest.GetRequestStream()
    !!> !> ! at
    !!> !> !System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    !!> !> !(String methodN
    !!> !> !ame, Object[] parameters)
    !!> !> ! at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    !!> !> !methodName, Object[] p
    !!> !> !arameters) in
    !!> !> !d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    !!> !> !:line 3
    !!> !> !
    !!> !> !
    !!> !>
    !!> !>
    !!> !
    !!> !
    !!> !
    !!>
    !!>
    !!
    !!
    !!
    !
    !
    !
    Yan-Hong Huang[MSFT], Jul 28, 2003
    #4
  5. Hello Joel,

    Our finding till now is that if we enlarge the maximum number of connections to a server or group of servers in the
    <connectionManagement> element defined in machine.config, the problem will be gone sometimes.

    We are checking dump of it now. Are you still monitoring the issue?

    Thanks very much.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !X-Tomcat-ID: 120066908
    !References: <05e601c34bee$8a519d50$> <>
    <#> <> <#sD2G3UUDHA.2368
    @TK2MSFTNGP09.phx.gbl> <>
    !MIME-Version: 1.0
    !Content-Type: text/plain
    !Content-Transfer-Encoding: 7bit
    !From: (Yan-Hong Huang[MSFT])
    !Organization: Microsoft
    !Date: Mon, 28 Jul 2003 06:31:12 GMT
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !Message-ID: <>
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !Lines: 269
    !Path: cpmsftngxa06.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18491
    !NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
    !
    !Hi Joel,
    !
    !We are still performing research on it. It may need some more time. Sorry for any inconvenience.
    !
    !Best regards,
    !Yanhong Huang
    !Microsoft Online Partner Support
    !
    !Get Secure! - www.microsoft.com/security
    !This posting is provided "AS IS" with no warranties, and confers no rights.
    !
    !--------------------
    !!X-Tomcat-ID: 243274584
    !!References: <05e601c34bee$8a519d50$> <>
    !<#> <>
    <#sD2G3UUDHA.2368
    !@TK2MSFTNGP09.phx.gbl>
    !!MIME-Version: 1.0
    !!Content-Type: text/plain
    !!Content-Transfer-Encoding: 7bit
    !!From: (Yan-Hong Huang[MSFT])
    !!Organization: Microsoft
    !!Date: Thu, 24 Jul 2003 09:54:36 GMT
    !!Subject: Re: "The operation has timed-out." exception on WinXP
    !!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !!Message-ID: <>
    !!Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !!Lines: 232
    !!Path: cpmsftngxa06.phx.gbl
    !!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18442
    !!NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
    !!
    !!Hello Joel,
    !!
    !!I did reproduce it on my side. The next exception (timed-out) happens after each 403 error. I will dig into it and reply you with
    !!more information on it.
    !!
    !!Thanks very much.
    !!
    !!Best regards,
    !!Yanhong Huang
    !!Microsoft Online Partner Support
    !!
    !!Get Secure! - www.microsoft.com/security
    !!This posting is provided "AS IS" with no warranties, and confers no rights.
    !!
    !!--------------------
    !!!Reply-To: "Joel Zhou" <>
    !!!From: "Joel Zhou" <>
    !!!References: <05e601c34bee$8a519d50$> <>
    !!<#> <>
    !!!Subject: Re: "The operation has timed-out." exception on WinXP
    !!!Date: Wed, 23 Jul 2003 14:06:32 -0500
    !!!Lines: 217
    !!!X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !!!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !!!Message-ID: <#>
    !!!Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !!!NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !!!Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
    !!!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18428
    !!!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !!!
    !!!Hi Yanhong,
    !!!
    !!!I tried to simplify the problem by creating a web service, and then added
    !!!web reference of this web service in a C# console test client. I did not put
    !!!my custom Invoke in the proxy this time. I kept the IIS busy by launching a
    !!!web client and kept the current connection at 10 (maximum allowed by WinXP).
    !!!When I launch the test client, I got the following exception one after
    !!!another:
    !!!The request failed with HTTP status 403: Access Forbidden.
    !!!The operation has timed-out.
    !!!The request failed with HTTP status 403: Access Forbidden.
    !!!The operation has timed-out.
    !!!...
    !!!
    !!!In the test client, the code is simply calling the same method on the web
    !!!service in a while loop.
    !!!
    !!!localhost.Service1 webProxy = new localhost.Service1();
    !!!while (true)
    !!!{
    !!! try
    !!! {
    !!! string result = webProxy.Sleep(1000);
    !!! Console.WriteLine("Done. Result = {0}", result);
    !!! }
    !!! catch(Exception e)
    !!! {
    !!! Console.WriteLine("Failed. Exception={0}", e.Message);
    !!! }
    !!!}
    !!!return;
    !!!
    !!!Thanks for your help,
    !!!Joel
    !!!
    !!!
    !!!
    !!!"Yan-Hong Huang[MSFT]" <> wrote in message
    !!!news:...
    !!!> Hello Joel,
    !!!>
    !!!> Then if you remove this part of code, did you meet this problem? We need
    !!!to isolate the problem before digging into it. :)
    !!!> Thanks very much.
    !!!>
    !!!> Best regards,
    !!!> Yanhong Huang
    !!!> Microsoft Online Partner Support
    !!!>
    !!!> Get Secure! - www.microsoft.com/security
    !!!> This posting is provided "AS IS" with no warranties, and confers no
    !!!rights.
    !!!>
    !!!> --------------------
    !!!> !Reply-To: "Joel Zhou" <>
    !!!> !From: "Joel Zhou" <>
    !!!> !References: <05e601c34bee$8a519d50$>
    !!!<>
    !!!> !Subject: Re: "The operation has timed-out." exception on WinXP
    !!!> !Date: Fri, 18 Jul 2003 11:32:18 -0500
    !!!> !Lines: 137
    !!!> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !!!> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !!!> !Message-ID: <#>
    !!!> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !!!> !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !!!> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    !!!> !Xref: cpmsftngxa06.phx.gbl
    !!!microsoft.public.dotnet.framework.aspnet.webservices:18362
    !!!> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !!!> !
    !!!> !Hi Yanhong,
    !!!> !
    !!!> !Thank you for the reply. I did not explicitly open any handle so I am not
    !!!> !sure if I what I need to close.
    !!!> !
    !!!> !In my web proxy class, I created a new Invoke method to replace the base
    !!!> !class's Invoke method. In my Invoke method, I call the base class's
    !!!Invoke,
    !!!> !and added retry if base class's Invoke throws exception. So when IIS
    !!!stays
    !!!> !busy with 10 connections, my Invoke will automatically retry - sleep -
    !!!> !retry - sleep ... for up to MaxRetry.
    !!!> !
    !!!> !// Replace the base class's Invoke.
    !!!> !protected new object[] Invoke(string methodName, object[] parameters)
    !!!> ! {
    !!!> ! object[] results = null;
    !!!> ! int nRetries = 0;
    !!!> ! do
    !!!> ! {
    !!!> ! try
    !!!> ! {
    !!!> ! results = base.Invoke(methodName, parameters);
    !!!> ! // if we do not have an exception, we will exit the
    !!!> !while loop now.
    !!!> ! break;
    !!!> ! }
    !!!> ! catch(System.Net.WebException webExp)
    !!!> ! {
    !!!> ! // On WinXP, this could be "The request failed with
    !!!HTTP
    !!!> !status 403: Access Forbidden"
    !!!> ! // This also could be ""The operation has timed-out."
    !!!> ! // we need to retry in both cases
    !!!> ! if (nRetries==MaxRetry)
    !!!> ! {
    !!!> ! throw webExp;
    !!!> ! }
    !!!> ! else
    !!!> ! {
    !!!> ! // sleep sometime before retrying
    !!!> ! System.Threading.Thread.Sleep(RetryInterval);
    !!!> ! }
    !!!> ! }
    !!!> ! nRetries++;
    !!!> ! }while(this.EnableRetry==true);
    !!!> !
    !!!> ! return results;
    !!!> ! }
    !!!> !
    !!!> !
    !!!> !Thanks
    !!!> !Joel Zhou
    !!!> !
    !!!> !
    !!!> !
    !!!> !"Yan-Hong Huang[MSFT]" <> wrote in message
    !!!> !news:...
    !!!> !> Hello Joel,
    !!!> !>
    !!!> !> I can't tell exactly where the problem exists now. Have you confirmed
    !!!that
    !!!> !you have closed all the handles, such as stream
    !!!> !> handles, and etc.
    !!!> !>
    !!!> !> Thanks.
    !!!> !>
    !!!> !> Best regards,
    !!!> !> Yanhong Huang
    !!!> !> Microsoft Online Partner Support
    !!!> !>
    !!!> !> Get Secure! - www.microsoft.com/security
    !!!> !> This posting is provided "AS IS" with no warranties, and confers no
    !!!> !rights.
    !!!> !>
    !!!> !> --------------------
    !!!> !> !Content-Class: urn:content-classes:message
    !!!> !> !From: "Joel Zhou" <>
    !!!> !> !Sender: "Joel Zhou" <>
    !!!> !> !Subject: "The operation has timed-out." exception on WinXP
    !!!> !> !Date: Wed, 16 Jul 2003 16:03:59 -0700
    !!!> !> !Lines: 39
    !!!> !> !Message-ID: <05e601c34bee$8a519d50$>
    !!!> !> !MIME-Version: 1.0
    !!!> !> !Content-Type: text/plain;
    !!!> !> ! charset="iso-8859-1"
    !!!> !> !Content-Transfer-Encoding: 7bit
    !!!> !> !X-Newsreader: Microsoft CDO for Windows 2000
    !!!> !> !X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    !!!> !> !Thread-Index: AcNL7opR4m2aDJgCSfSToDfa2GQ+3A==
    !!!> !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !!!> !> !Path: cpmsftngxa06.phx.gbl
    !!!> !> !Xref: cpmsftngxa06.phx.gbl
    !!!> !microsoft.public.dotnet.framework.aspnet.webservices:18319
    !!!> !> !NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    !!!> !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !!!> !> !
    !!!> !> !Our web clients makes synchronous web method calls to a
    !!!> !> !web service on a XP workstation, running .Net 1.1.4322.
    !!!> !> !
    !!!> !> !When there are already 10 connections to the IIS, the
    !!!> !> !client gets "The request failed with HTTP status 403:
    !!!> !> !Access Forbidden." when calling the web service. This is
    !!!> !> !expected behavior documented by MSDN. However, my problem
    !!!> !> !is if the client (same thread) tries to make the call
    !!!> !> !again after the total connection < 10, it will get "The
    !!!> !> !operation has timed-out." exception first, and then if the
    !!!> !> !client makes the same call again, it will work.
    !!!> !> !
    !!!> !> !If the IIS connection stays at 10, the client will get
    !!!> !> !those two exceptions one after another. I am expecting the
    !!!> !> !client to always get the "..Access Forbidden" exception.
    !!!> !> !
    !!!> !> !It seems that after the "...403: Access Forbidden" error,
    !!!> !> !the client will always get a "The operation has timed-
    !!!> !> !out." before it will work again. I set the client side
    !!!> !> !timeout to 30 seconds. The timeout exception happens about
    !!!> !> !90 seconds after making the call.
    !!!> !> !
    !!!> !> !I am trying to figure out how to avoid the timeout
    !!!> !> !exception. Any suggestions?
    !!!> !> !
    !!!> !> !The exception call stack is below:
    !!!> !> !Error: System.Net.WebException: The operation has timed-
    !!!> !> !out.
    !!!> !> ! at System.Net.HttpWebRequest.GetRequestStream()
    !!!> !> ! at
    !!!> !> !System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    !!!> !> !(String methodN
    !!!> !> !ame, Object[] parameters)
    !!!> !> ! at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    !!!> !> !methodName, Object[] p
    !!!> !> !arameters) in
    !!!> !> !d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    !!!> !> !:line 3
    !!!> !> !
    !!!> !> !
    !!!> !>
    !!!> !>
    !!!> !
    !!!> !
    !!!> !
    !!!>
    !!!>
    !!!
    !!!
    !!!
    !!
    !!
    !!
    !
    !
    !
    Yan-Hong Huang[MSFT], Jul 30, 2003
    #5
  6. Hello Joel,

    Based on our testing, the error is related to the release of connection. After we upgrade to VS.NET 2003 and .net framework
    1.1, the problem is gone. Could you please test it in VS.NET 2003 and let us know your testing result?

    Thanks very much.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !Reply-To: "Joel Zhou" <>
    !From: "Joel Zhou" <>
    !References: <05e601c34bee$8a519d50$> <>
    <#> <>
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !Date: Wed, 23 Jul 2003 14:06:32 -0500
    !Lines: 217
    !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !Message-ID: <#>
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18428
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !
    !Hi Yanhong,
    !
    !I tried to simplify the problem by creating a web service, and then added
    !web reference of this web service in a C# console test client. I did not put
    !my custom Invoke in the proxy this time. I kept the IIS busy by launching a
    !web client and kept the current connection at 10 (maximum allowed by WinXP).
    !When I launch the test client, I got the following exception one after
    !another:
    !The request failed with HTTP status 403: Access Forbidden.
    !The operation has timed-out.
    !The request failed with HTTP status 403: Access Forbidden.
    !The operation has timed-out.
    !...
    !
    !In the test client, the code is simply calling the same method on the web
    !service in a while loop.
    !
    !localhost.Service1 webProxy = new localhost.Service1();
    !while (true)
    !{
    ! try
    ! {
    ! string result = webProxy.Sleep(1000);
    ! Console.WriteLine("Done. Result = {0}", result);
    ! }
    ! catch(Exception e)
    ! {
    ! Console.WriteLine("Failed. Exception={0}", e.Message);
    ! }
    !}
    !return;
    !
    !Thanks for your help,
    !Joel
    !
    !
    !
    !"Yan-Hong Huang[MSFT]" <> wrote in message
    !news:...
    !> Hello Joel,
    !>
    !> Then if you remove this part of code, did you meet this problem? We need
    !to isolate the problem before digging into it. :)
    !> Thanks very much.
    !>
    !> Best regards,
    !> Yanhong Huang
    !> Microsoft Online Partner Support
    !>
    !> Get Secure! - www.microsoft.com/security
    !> This posting is provided "AS IS" with no warranties, and confers no
    !rights.
    !>
    !> --------------------
    !> !Reply-To: "Joel Zhou" <>
    !> !From: "Joel Zhou" <>
    !> !References: <05e601c34bee$8a519d50$>
    !<>
    !> !Subject: Re: "The operation has timed-out." exception on WinXP
    !> !Date: Fri, 18 Jul 2003 11:32:18 -0500
    !> !Lines: 137
    !> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    !> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    !> !Message-ID: <#>
    !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !> !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    !> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    !> !Xref: cpmsftngxa06.phx.gbl
    !microsoft.public.dotnet.framework.aspnet.webservices:18362
    !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !> !
    !> !Hi Yanhong,
    !> !
    !> !Thank you for the reply. I did not explicitly open any handle so I am not
    !> !sure if I what I need to close.
    !> !
    !> !In my web proxy class, I created a new Invoke method to replace the base
    !> !class's Invoke method. In my Invoke method, I call the base class's
    !Invoke,
    !> !and added retry if base class's Invoke throws exception. So when IIS
    !stays
    !> !busy with 10 connections, my Invoke will automatically retry - sleep -
    !> !retry - sleep ... for up to MaxRetry.
    !> !
    !> !// Replace the base class's Invoke.
    !> !protected new object[] Invoke(string methodName, object[] parameters)
    !> ! {
    !> ! object[] results = null;
    !> ! int nRetries = 0;
    !> ! do
    !> ! {
    !> ! try
    !> ! {
    !> ! results = base.Invoke(methodName, parameters);
    !> ! // if we do not have an exception, we will exit the
    !> !while loop now.
    !> ! break;
    !> ! }
    !> ! catch(System.Net.WebException webExp)
    !> ! {
    !> ! // On WinXP, this could be "The request failed with
    !HTTP
    !> !status 403: Access Forbidden"
    !> ! // This also could be ""The operation has timed-out."
    !> ! // we need to retry in both cases
    !> ! if (nRetries==MaxRetry)
    !> ! {
    !> ! throw webExp;
    !> ! }
    !> ! else
    !> ! {
    !> ! // sleep sometime before retrying
    !> ! System.Threading.Thread.Sleep(RetryInterval);
    !> ! }
    !> ! }
    !> ! nRetries++;
    !> ! }while(this.EnableRetry==true);
    !> !
    !> ! return results;
    !> ! }
    !> !
    !> !
    !> !Thanks
    !> !Joel Zhou
    !> !
    !> !
    !> !
    !> !"Yan-Hong Huang[MSFT]" <> wrote in message
    !> !news:...
    !> !> Hello Joel,
    !> !>
    !> !> I can't tell exactly where the problem exists now. Have you confirmed
    !that
    !> !you have closed all the handles, such as stream
    !> !> handles, and etc.
    !> !>
    !> !> Thanks.
    !> !>
    !> !> Best regards,
    !> !> Yanhong Huang
    !> !> Microsoft Online Partner Support
    !> !>
    !> !> Get Secure! - www.microsoft.com/security
    !> !> This posting is provided "AS IS" with no warranties, and confers no
    !> !rights.
    !> !>
    !> !> --------------------
    !> !> !Content-Class: urn:content-classes:message
    !> !> !From: "Joel Zhou" <>
    !> !> !Sender: "Joel Zhou" <>
    !> !> !Subject: "The operation has timed-out." exception on WinXP
    !> !> !Date: Wed, 16 Jul 2003 16:03:59 -0700
    !> !> !Lines: 39
    !> !> !Message-ID: <05e601c34bee$8a519d50$>
    !> !> !MIME-Version: 1.0
    !> !> !Content-Type: text/plain;
    !> !> ! charset="iso-8859-1"
    !> !> !Content-Transfer-Encoding: 7bit
    !> !> !X-Newsreader: Microsoft CDO for Windows 2000
    !> !> !X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    !> !> !Thread-Index: AcNL7opR4m2aDJgCSfSToDfa2GQ+3A==
    !> !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !> !> !Path: cpmsftngxa06.phx.gbl
    !> !> !Xref: cpmsftngxa06.phx.gbl
    !> !microsoft.public.dotnet.framework.aspnet.webservices:18319
    !> !> !NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    !> !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !> !> !
    !> !> !Our web clients makes synchronous web method calls to a
    !> !> !web service on a XP workstation, running .Net 1.1.4322.
    !> !> !
    !> !> !When there are already 10 connections to the IIS, the
    !> !> !client gets "The request failed with HTTP status 403:
    !> !> !Access Forbidden." when calling the web service. This is
    !> !> !expected behavior documented by MSDN. However, my problem
    !> !> !is if the client (same thread) tries to make the call
    !> !> !again after the total connection < 10, it will get "The
    !> !> !operation has timed-out." exception first, and then if the
    !> !> !client makes the same call again, it will work.
    !> !> !
    !> !> !If the IIS connection stays at 10, the client will get
    !> !> !those two exceptions one after another. I am expecting the
    !> !> !client to always get the "..Access Forbidden" exception.
    !> !> !
    !> !> !It seems that after the "...403: Access Forbidden" error,
    !> !> !the client will always get a "The operation has timed-
    !> !> !out." before it will work again. I set the client side
    !> !> !timeout to 30 seconds. The timeout exception happens about
    !> !> !90 seconds after making the call.
    !> !> !
    !> !> !I am trying to figure out how to avoid the timeout
    !> !> !exception. Any suggestions?
    !> !> !
    !> !> !The exception call stack is below:
    !> !> !Error: System.Net.WebException: The operation has timed-
    !> !> !out.
    !> !> ! at System.Net.HttpWebRequest.GetRequestStream()
    !> !> ! at
    !> !> !System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    !> !> !(String methodN
    !> !> !ame, Object[] parameters)
    !> !> ! at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    !> !> !methodName, Object[] p
    !> !> !arameters) in
    !> !> !d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    !> !> !:line 3
    !> !> !
    !> !> !
    !> !>
    !> !>
    !> !
    !> !
    !> !
    !>
    !>
    !
    !
    !
    Yan-Hong Huang[MSFT], Jul 30, 2003
    #6
  7. >
    >Based on our testing, the error is related to the release of connection. After we upgrade to VS.NET 2003 and .net framework
    >1.1, the problem is gone. Could you please test it in VS.NET 2003 and let us know your testing result?
    >


    Folks,

    writing in this thread to let you know that we are having a simmilar
    problem with the GetRequestStream() call. It´s not about web services
    but I call another webserver from an ASP.NET application. This call
    seems to time out on every second request. Seems another call is
    possible only after the worker process gets recycled. Compiled with
    VS.NET 2002.
    Now off to install 2003 to see if it works then...

    Daniel
    Daniel Buchholz, Jul 30, 2003
    #7
  8. On Wed, 30 Jul 2003 13:24:08 GMT, (Daniel
    Buchholz) wrote:

    >Now off to install 2003 to see if it works then...


    Me again!

    No luck. :-( Used VS.NET 2003 to compile the ASP.NET application but
    we still get the timeout on the second request.

    Daniel
    Daniel Buchholz, Jul 30, 2003
    #8
  9. Joel Zhou

    Joel Zhou Guest

    Yanhong,

    Thank you for your effort. I am still monitoring the thread and I will try
    VS.Net 2003.

    Thanks,
    Joel

    "Yan-Hong Huang[MSFT]" <> wrote in message
    news:...
    > Hello Joel,
    >
    > Our finding till now is that if we enlarge the maximum number of

    connections to a server or group of servers in the
    > <connectionManagement> element defined in machine.config, the problem will

    be gone sometimes.
    >
    > We are checking dump of it now. Are you still monitoring the issue?
    >
    > Thanks very much.
    >
    > Best regards,
    > Yanhong Huang
    > Microsoft Online Partner Support
    >
    > Get Secure! - www.microsoft.com/security
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    >
    > --------------------
    > !X-Tomcat-ID: 120066908
    > !References: <05e601c34bee$8a519d50$>

    <>
    > <#>

    <> <#sD2G3UUDHA.2368
    > @TK2MSFTNGP09.phx.gbl> <>
    > !MIME-Version: 1.0
    > !Content-Type: text/plain
    > !Content-Transfer-Encoding: 7bit
    > !From: (Yan-Hong Huang[MSFT])
    > !Organization: Microsoft
    > !Date: Mon, 28 Jul 2003 06:31:12 GMT
    > !Subject: Re: "The operation has timed-out." exception on WinXP
    > !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !Message-ID: <>
    > !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !Lines: 269
    > !Path: cpmsftngxa06.phx.gbl
    > !Xref: cpmsftngxa06.phx.gbl

    microsoft.public.dotnet.framework.aspnet.webservices:18491
    > !NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
    > !
    > !Hi Joel,
    > !
    > !We are still performing research on it. It may need some more time. Sorry

    for any inconvenience.
    > !
    > !Best regards,
    > !Yanhong Huang
    > !Microsoft Online Partner Support
    > !
    > !Get Secure! - www.microsoft.com/security
    > !This posting is provided "AS IS" with no warranties, and confers no

    rights.
    > !
    > !--------------------
    > !!X-Tomcat-ID: 243274584
    > !!References: <05e601c34bee$8a519d50$>

    <>
    > !<#>

    <>
    > <#sD2G3UUDHA.2368
    > !@TK2MSFTNGP09.phx.gbl>
    > !!MIME-Version: 1.0
    > !!Content-Type: text/plain
    > !!Content-Transfer-Encoding: 7bit
    > !!From: (Yan-Hong Huang[MSFT])
    > !!Organization: Microsoft
    > !!Date: Thu, 24 Jul 2003 09:54:36 GMT
    > !!Subject: Re: "The operation has timed-out." exception on WinXP
    > !!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !!Message-ID: <>
    > !!Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !!Lines: 232
    > !!Path: cpmsftngxa06.phx.gbl
    > !!Xref: cpmsftngxa06.phx.gbl

    microsoft.public.dotnet.framework.aspnet.webservices:18442
    > !!NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
    > !!
    > !!Hello Joel,
    > !!
    > !!I did reproduce it on my side. The next exception (timed-out) happens

    after each 403 error. I will dig into it and reply you with
    > !!more information on it.
    > !!
    > !!Thanks very much.
    > !!
    > !!Best regards,
    > !!Yanhong Huang
    > !!Microsoft Online Partner Support
    > !!
    > !!Get Secure! - www.microsoft.com/security
    > !!This posting is provided "AS IS" with no warranties, and confers no

    rights.
    > !!
    > !!--------------------
    > !!!Reply-To: "Joel Zhou" <>
    > !!!From: "Joel Zhou" <>
    > !!!References: <05e601c34bee$8a519d50$>

    <>
    > !!<#>

    <>
    > !!!Subject: Re: "The operation has timed-out." exception on WinXP
    > !!!Date: Wed, 23 Jul 2003 14:06:32 -0500
    > !!!Lines: 217
    > !!!X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    > !!!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    > !!!Message-ID: <#>
    > !!!Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !!!NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    > !!!Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
    > !!!Xref: cpmsftngxa06.phx.gbl

    microsoft.public.dotnet.framework.aspnet.webservices:18428
    > !!!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !!!
    > !!!Hi Yanhong,
    > !!!
    > !!!I tried to simplify the problem by creating a web service, and then

    added
    > !!!web reference of this web service in a C# console test client. I did

    not put
    > !!!my custom Invoke in the proxy this time. I kept the IIS busy by

    launching a
    > !!!web client and kept the current connection at 10 (maximum allowed by

    WinXP).
    > !!!When I launch the test client, I got the following exception one after
    > !!!another:
    > !!!The request failed with HTTP status 403: Access Forbidden.
    > !!!The operation has timed-out.
    > !!!The request failed with HTTP status 403: Access Forbidden.
    > !!!The operation has timed-out.
    > !!!...
    > !!!
    > !!!In the test client, the code is simply calling the same method on the

    web
    > !!!service in a while loop.
    > !!!
    > !!!localhost.Service1 webProxy = new localhost.Service1();
    > !!!while (true)
    > !!!{
    > !!! try
    > !!! {
    > !!! string result = webProxy.Sleep(1000);
    > !!! Console.WriteLine("Done. Result = {0}", result);
    > !!! }
    > !!! catch(Exception e)
    > !!! {
    > !!! Console.WriteLine("Failed. Exception={0}", e.Message);
    > !!! }
    > !!!}
    > !!!return;
    > !!!
    > !!!Thanks for your help,
    > !!!Joel
    > !!!
    > !!!
    > !!!
    > !!!"Yan-Hong Huang[MSFT]" <> wrote in message
    > !!!news:...
    > !!!> Hello Joel,
    > !!!>
    > !!!> Then if you remove this part of code, did you meet this problem? We

    need
    > !!!to isolate the problem before digging into it. :)
    > !!!> Thanks very much.
    > !!!>
    > !!!> Best regards,
    > !!!> Yanhong Huang
    > !!!> Microsoft Online Partner Support
    > !!!>
    > !!!> Get Secure! - www.microsoft.com/security
    > !!!> This posting is provided "AS IS" with no warranties, and confers no
    > !!!rights.
    > !!!>
    > !!!> --------------------
    > !!!> !Reply-To: "Joel Zhou" <>
    > !!!> !From: "Joel Zhou" <>
    > !!!> !References: <05e601c34bee$8a519d50$>
    > !!!<>
    > !!!> !Subject: Re: "The operation has timed-out." exception on WinXP
    > !!!> !Date: Fri, 18 Jul 2003 11:32:18 -0500
    > !!!> !Lines: 137
    > !!!> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    > !!!> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    > !!!> !Message-ID: <#>
    > !!!> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !!!> !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    > !!!> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    > !!!> !Xref: cpmsftngxa06.phx.gbl
    > !!!microsoft.public.dotnet.framework.aspnet.webservices:18362
    > !!!> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !!!> !
    > !!!> !Hi Yanhong,
    > !!!> !
    > !!!> !Thank you for the reply. I did not explicitly open any handle so I

    am not
    > !!!> !sure if I what I need to close.
    > !!!> !
    > !!!> !In my web proxy class, I created a new Invoke method to replace the

    base
    > !!!> !class's Invoke method. In my Invoke method, I call the base class's
    > !!!Invoke,
    > !!!> !and added retry if base class's Invoke throws exception. So when IIS
    > !!!stays
    > !!!> !busy with 10 connections, my Invoke will automatically retry -

    sleep -
    > !!!> !retry - sleep ... for up to MaxRetry.
    > !!!> !
    > !!!> !// Replace the base class's Invoke.
    > !!!> !protected new object[] Invoke(string methodName, object[]

    parameters)
    > !!!> ! {
    > !!!> ! object[] results = null;
    > !!!> ! int nRetries = 0;
    > !!!> ! do
    > !!!> ! {
    > !!!> ! try
    > !!!> ! {
    > !!!> ! results = base.Invoke(methodName, parameters);
    > !!!> ! // if we do not have an exception, we will exit

    the
    > !!!> !while loop now.
    > !!!> ! break;
    > !!!> ! }
    > !!!> ! catch(System.Net.WebException webExp)
    > !!!> ! {
    > !!!> ! // On WinXP, this could be "The request failed

    with
    > !!!HTTP
    > !!!> !status 403: Access Forbidden"
    > !!!> ! // This also could be ""The operation has

    timed-out."
    > !!!> ! // we need to retry in both cases
    > !!!> ! if (nRetries==MaxRetry)
    > !!!> ! {
    > !!!> ! throw webExp;
    > !!!> ! }
    > !!!> ! else
    > !!!> ! {
    > !!!> ! // sleep sometime before retrying
    > !!!> !

    System.Threading.Thread.Sleep(RetryInterval);
    > !!!> ! }
    > !!!> ! }
    > !!!> ! nRetries++;
    > !!!> ! }while(this.EnableRetry==true);
    > !!!> !
    > !!!> ! return results;
    > !!!> ! }
    > !!!> !
    > !!!> !
    > !!!> !Thanks
    > !!!> !Joel Zhou
    > !!!> !
    > !!!> !
    > !!!> !
    > !!!> !"Yan-Hong Huang[MSFT]" <> wrote in

    message
    > !!!> !news:...
    > !!!> !> Hello Joel,
    > !!!> !>
    > !!!> !> I can't tell exactly where the problem exists now. Have you

    confirmed
    > !!!that
    > !!!> !you have closed all the handles, such as stream
    > !!!> !> handles, and etc.
    > !!!> !>
    > !!!> !> Thanks.
    > !!!> !>
    > !!!> !> Best regards,
    > !!!> !> Yanhong Huang
    > !!!> !> Microsoft Online Partner Support
    > !!!> !>
    > !!!> !> Get Secure! - www.microsoft.com/security
    > !!!> !> This posting is provided "AS IS" with no warranties, and confers

    no
    > !!!> !rights.
    > !!!> !>
    > !!!> !> --------------------
    > !!!> !> !Content-Class: urn:content-classes:message
    > !!!> !> !From: "Joel Zhou" <>
    > !!!> !> !Sender: "Joel Zhou" <>
    > !!!> !> !Subject: "The operation has timed-out." exception on WinXP
    > !!!> !> !Date: Wed, 16 Jul 2003 16:03:59 -0700
    > !!!> !> !Lines: 39
    > !!!> !> !Message-ID: <05e601c34bee$8a519d50$>
    > !!!> !> !MIME-Version: 1.0
    > !!!> !> !Content-Type: text/plain;
    > !!!> !> ! charset="iso-8859-1"
    > !!!> !> !Content-Transfer-Encoding: 7bit
    > !!!> !> !X-Newsreader: Microsoft CDO for Windows 2000
    > !!!> !> !X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    > !!!> !> !Thread-Index: AcNL7opR4m2aDJgCSfSToDfa2GQ+3A==
    > !!!> !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !!!> !> !Path: cpmsftngxa06.phx.gbl
    > !!!> !> !Xref: cpmsftngxa06.phx.gbl
    > !!!> !microsoft.public.dotnet.framework.aspnet.webservices:18319
    > !!!> !> !NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    > !!!> !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !!!> !> !
    > !!!> !> !Our web clients makes synchronous web method calls to a
    > !!!> !> !web service on a XP workstation, running .Net 1.1.4322.
    > !!!> !> !
    > !!!> !> !When there are already 10 connections to the IIS, the
    > !!!> !> !client gets "The request failed with HTTP status 403:
    > !!!> !> !Access Forbidden." when calling the web service. This is
    > !!!> !> !expected behavior documented by MSDN. However, my problem
    > !!!> !> !is if the client (same thread) tries to make the call
    > !!!> !> !again after the total connection < 10, it will get "The
    > !!!> !> !operation has timed-out." exception first, and then if the
    > !!!> !> !client makes the same call again, it will work.
    > !!!> !> !
    > !!!> !> !If the IIS connection stays at 10, the client will get
    > !!!> !> !those two exceptions one after another. I am expecting the
    > !!!> !> !client to always get the "..Access Forbidden" exception.
    > !!!> !> !
    > !!!> !> !It seems that after the "...403: Access Forbidden" error,
    > !!!> !> !the client will always get a "The operation has timed-
    > !!!> !> !out." before it will work again. I set the client side
    > !!!> !> !timeout to 30 seconds. The timeout exception happens about
    > !!!> !> !90 seconds after making the call.
    > !!!> !> !
    > !!!> !> !I am trying to figure out how to avoid the timeout
    > !!!> !> !exception. Any suggestions?
    > !!!> !> !
    > !!!> !> !The exception call stack is below:
    > !!!> !> !Error: System.Net.WebException: The operation has timed-
    > !!!> !> !out.
    > !!!> !> ! at System.Net.HttpWebRequest.GetRequestStream()
    > !!!> !> ! at
    > !!!> !> !System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    > !!!> !> !(String methodN
    > !!!> !> !ame, Object[] parameters)
    > !!!> !> ! at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    > !!!> !> !methodName, Object[] p
    > !!!> !> !arameters) in
    > !!!> !> !d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    > !!!> !> !:line 3
    > !!!> !> !
    > !!!> !> !
    > !!!> !>
    > !!!> !>
    > !!!> !
    > !!!> !
    > !!!> !
    > !!!>
    > !!!>
    > !!!
    > !!!
    > !!!
    > !!
    > !!
    > !!
    > !
    > !
    > !
    >
    >
    Joel Zhou, Jul 30, 2003
    #9
  10. Hi Daniel,

    Have you tried to enlarge connections in connectionManagement in machine.config?

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !From: (Daniel Buchholz)
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !Date: Wed, 30 Jul 2003 14:27:29 GMT
    !Lines: 11
    !Message-ID: <>
    !References: <05e601c34bee$8a519d50$> <>
    <#> <> <#sD2G3UUDHA.2368
    @TK2MSFTNGP09.phx.gbl> <Lln$> <>
    !NNTP-Posting-Host: 145.228.10.180
    !X-Trace: news.uni-berlin.de 1059575249 23038788 145.228.10.180 (16 [53906])
    !X-Newsreader: Forte Free Agent 1.21/32.243
    !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!npeer.de.kpn-eurorings.net!fu-
    berlin.de!uni-berlin.de!145.228.10.180!not-for-mail
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18537
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !
    !On Wed, 30 Jul 2003 13:24:08 GMT, (Daniel
    !Buchholz) wrote:
    !
    !>Now off to install 2003 to see if it works then...
    !
    !Me again!
    !
    !No luck. :-( Used VS.NET 2003 to compile the ASP.NET application but
    !we still get the timeout on the second request.
    !
    !Daniel
    !
    Yan-Hong Huang[MSFT], Jul 31, 2003
    #10
  11. On Thu, 31 Jul 2003 08:10:07 GMT,
    (Yan-Hong Huang[MSFT]) wrote:

    >Hi Daniel,
    >
    >Have you tried to enlarge connections in connectionManagement in machine.config?
    >


    Yes, we did that and it helped only a little.

    Figured out in the last hour that we forgot to explicitly Close() the
    WebResponse object. Then the problems are gone. Without the call to
    Close the connections remain in the state CLOSE_WAIT in the output of
    netstat.

    Strange, as the application worked fine over the last days without the
    call to Close().

    Daniel
    Daniel Buchholz, Jul 31, 2003
    #11
  12. Joel Zhou

    Joel Zhou Guest

    Yanhong,

    VS.Net 2003 fixed the problem. Here is what I found:

    VS.Net 2003 + .Net runtime 1.1.4322 ---> works
    VS.Net 2002 + .Net runtime 1.1.4322 ---> does not work

    Looks like the VS.Net 2003 complier made a difference. We are shipping our
    product built with VS.Net 2002 (VS7.0), is there anything we can do to fix
    this problem?

    Thanks,
    Joel


    "Joel Zhou" <> wrote in message
    news:%...
    > Yanhong,
    >
    > Thank you for your effort. I am still monitoring the thread and I will try
    > VS.Net 2003.
    >
    > Thanks,
    > Joel
    >
    > "Yan-Hong Huang[MSFT]" <> wrote in message
    > news:...
    > > Hello Joel,
    > >
    > > Our finding till now is that if we enlarge the maximum number of

    > connections to a server or group of servers in the
    > > <connectionManagement> element defined in machine.config, the problem

    will
    > be gone sometimes.
    > >
    > > We are checking dump of it now. Are you still monitoring the issue?
    > >
    > > Thanks very much.
    > >
    > > Best regards,
    > > Yanhong Huang
    > > Microsoft Online Partner Support
    > >
    > > Get Secure! - www.microsoft.com/security
    > > This posting is provided "AS IS" with no warranties, and confers no

    > rights.
    > >
    > > --------------------
    > > !X-Tomcat-ID: 120066908
    > > !References: <05e601c34bee$8a519d50$>

    > <>
    > > <#>

    > <> <#sD2G3UUDHA.2368
    > > @TK2MSFTNGP09.phx.gbl> <>
    > > !MIME-Version: 1.0
    > > !Content-Type: text/plain
    > > !Content-Transfer-Encoding: 7bit
    > > !From: (Yan-Hong Huang[MSFT])
    > > !Organization: Microsoft
    > > !Date: Mon, 28 Jul 2003 06:31:12 GMT
    > > !Subject: Re: "The operation has timed-out." exception on WinXP
    > > !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > > !Message-ID: <>
    > > !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > > !Lines: 269
    > > !Path: cpmsftngxa06.phx.gbl
    > > !Xref: cpmsftngxa06.phx.gbl

    > microsoft.public.dotnet.framework.aspnet.webservices:18491
    > > !NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
    > > !
    > > !Hi Joel,
    > > !
    > > !We are still performing research on it. It may need some more time.

    Sorry
    > for any inconvenience.
    > > !
    > > !Best regards,
    > > !Yanhong Huang
    > > !Microsoft Online Partner Support
    > > !
    > > !Get Secure! - www.microsoft.com/security
    > > !This posting is provided "AS IS" with no warranties, and confers no

    > rights.
    > > !
    > > !--------------------
    > > !!X-Tomcat-ID: 243274584
    > > !!References: <05e601c34bee$8a519d50$>

    > <>
    > > !<#>

    > <>
    > > <#sD2G3UUDHA.2368
    > > !@TK2MSFTNGP09.phx.gbl>
    > > !!MIME-Version: 1.0
    > > !!Content-Type: text/plain
    > > !!Content-Transfer-Encoding: 7bit
    > > !!From: (Yan-Hong Huang[MSFT])
    > > !!Organization: Microsoft
    > > !!Date: Thu, 24 Jul 2003 09:54:36 GMT
    > > !!Subject: Re: "The operation has timed-out." exception on WinXP
    > > !!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > > !!Message-ID: <>
    > > !!Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > > !!Lines: 232
    > > !!Path: cpmsftngxa06.phx.gbl
    > > !!Xref: cpmsftngxa06.phx.gbl

    > microsoft.public.dotnet.framework.aspnet.webservices:18442
    > > !!NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
    > > !!
    > > !!Hello Joel,
    > > !!
    > > !!I did reproduce it on my side. The next exception (timed-out) happens

    > after each 403 error. I will dig into it and reply you with
    > > !!more information on it.
    > > !!
    > > !!Thanks very much.
    > > !!
    > > !!Best regards,
    > > !!Yanhong Huang
    > > !!Microsoft Online Partner Support
    > > !!
    > > !!Get Secure! - www.microsoft.com/security
    > > !!This posting is provided "AS IS" with no warranties, and confers no

    > rights.
    > > !!
    > > !!--------------------
    > > !!!Reply-To: "Joel Zhou" <>
    > > !!!From: "Joel Zhou" <>
    > > !!!References: <05e601c34bee$8a519d50$>

    > <>
    > > !!<#>

    > <>
    > > !!!Subject: Re: "The operation has timed-out." exception on WinXP
    > > !!!Date: Wed, 23 Jul 2003 14:06:32 -0500
    > > !!!Lines: 217
    > > !!!X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    > > !!!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    > > !!!Message-ID: <#>
    > > !!!Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > > !!!NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    > > !!!Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
    > > !!!Xref: cpmsftngxa06.phx.gbl

    > microsoft.public.dotnet.framework.aspnet.webservices:18428
    > > !!!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > > !!!
    > > !!!Hi Yanhong,
    > > !!!
    > > !!!I tried to simplify the problem by creating a web service, and then

    > added
    > > !!!web reference of this web service in a C# console test client. I did

    > not put
    > > !!!my custom Invoke in the proxy this time. I kept the IIS busy by

    > launching a
    > > !!!web client and kept the current connection at 10 (maximum allowed by

    > WinXP).
    > > !!!When I launch the test client, I got the following exception one

    after
    > > !!!another:
    > > !!!The request failed with HTTP status 403: Access Forbidden.
    > > !!!The operation has timed-out.
    > > !!!The request failed with HTTP status 403: Access Forbidden.
    > > !!!The operation has timed-out.
    > > !!!...
    > > !!!
    > > !!!In the test client, the code is simply calling the same method on the

    > web
    > > !!!service in a while loop.
    > > !!!
    > > !!!localhost.Service1 webProxy = new localhost.Service1();
    > > !!!while (true)
    > > !!!{
    > > !!! try
    > > !!! {
    > > !!! string result = webProxy.Sleep(1000);
    > > !!! Console.WriteLine("Done. Result = {0}", result);
    > > !!! }
    > > !!! catch(Exception e)
    > > !!! {
    > > !!! Console.WriteLine("Failed. Exception={0}", e.Message);
    > > !!! }
    > > !!!}
    > > !!!return;
    > > !!!
    > > !!!Thanks for your help,
    > > !!!Joel
    > > !!!
    > > !!!
    > > !!!
    > > !!!"Yan-Hong Huang[MSFT]" <> wrote in

    message
    > > !!!news:...
    > > !!!> Hello Joel,
    > > !!!>
    > > !!!> Then if you remove this part of code, did you meet this problem? We

    > need
    > > !!!to isolate the problem before digging into it. :)
    > > !!!> Thanks very much.
    > > !!!>
    > > !!!> Best regards,
    > > !!!> Yanhong Huang
    > > !!!> Microsoft Online Partner Support
    > > !!!>
    > > !!!> Get Secure! - www.microsoft.com/security
    > > !!!> This posting is provided "AS IS" with no warranties, and confers no
    > > !!!rights.
    > > !!!>
    > > !!!> --------------------
    > > !!!> !Reply-To: "Joel Zhou" <>
    > > !!!> !From: "Joel Zhou" <>
    > > !!!> !References: <05e601c34bee$8a519d50$>
    > > !!!<>
    > > !!!> !Subject: Re: "The operation has timed-out." exception on WinXP
    > > !!!> !Date: Fri, 18 Jul 2003 11:32:18 -0500
    > > !!!> !Lines: 137
    > > !!!> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
    > > !!!> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
    > > !!!> !Message-ID: <#>
    > > !!!> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > > !!!> !NNTP-Posting-Host: fishrose-cp.frco.com 206.242.150.66
    > > !!!> !Path:

    cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    > > !!!> !Xref: cpmsftngxa06.phx.gbl
    > > !!!microsoft.public.dotnet.framework.aspnet.webservices:18362
    > > !!!> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > > !!!> !
    > > !!!> !Hi Yanhong,
    > > !!!> !
    > > !!!> !Thank you for the reply. I did not explicitly open any handle so I

    > am not
    > > !!!> !sure if I what I need to close.
    > > !!!> !
    > > !!!> !In my web proxy class, I created a new Invoke method to replace

    the
    > base
    > > !!!> !class's Invoke method. In my Invoke method, I call the base

    class's
    > > !!!Invoke,
    > > !!!> !and added retry if base class's Invoke throws exception. So when

    IIS
    > > !!!stays
    > > !!!> !busy with 10 connections, my Invoke will automatically retry -

    > sleep -
    > > !!!> !retry - sleep ... for up to MaxRetry.
    > > !!!> !
    > > !!!> !// Replace the base class's Invoke.
    > > !!!> !protected new object[] Invoke(string methodName, object[]

    > parameters)
    > > !!!> ! {
    > > !!!> ! object[] results = null;
    > > !!!> ! int nRetries = 0;
    > > !!!> ! do
    > > !!!> ! {
    > > !!!> ! try
    > > !!!> ! {
    > > !!!> ! results = base.Invoke(methodName, parameters);
    > > !!!> ! // if we do not have an exception, we will

    exit
    > the
    > > !!!> !while loop now.
    > > !!!> ! break;
    > > !!!> ! }
    > > !!!> ! catch(System.Net.WebException webExp)
    > > !!!> ! {
    > > !!!> ! // On WinXP, this could be "The request failed

    > with
    > > !!!HTTP
    > > !!!> !status 403: Access Forbidden"
    > > !!!> ! // This also could be ""The operation has

    > timed-out."
    > > !!!> ! // we need to retry in both cases
    > > !!!> ! if (nRetries==MaxRetry)
    > > !!!> ! {
    > > !!!> ! throw webExp;
    > > !!!> ! }
    > > !!!> ! else
    > > !!!> ! {
    > > !!!> ! // sleep sometime before retrying
    > > !!!> !

    > System.Threading.Thread.Sleep(RetryInterval);
    > > !!!> ! }
    > > !!!> ! }
    > > !!!> ! nRetries++;
    > > !!!> ! }while(this.EnableRetry==true);
    > > !!!> !
    > > !!!> ! return results;
    > > !!!> ! }
    > > !!!> !
    > > !!!> !
    > > !!!> !Thanks
    > > !!!> !Joel Zhou
    > > !!!> !
    > > !!!> !
    > > !!!> !
    > > !!!> !"Yan-Hong Huang[MSFT]" <> wrote in

    > message
    > > !!!> !news:...
    > > !!!> !> Hello Joel,
    > > !!!> !>
    > > !!!> !> I can't tell exactly where the problem exists now. Have you

    > confirmed
    > > !!!that
    > > !!!> !you have closed all the handles, such as stream
    > > !!!> !> handles, and etc.
    > > !!!> !>
    > > !!!> !> Thanks.
    > > !!!> !>
    > > !!!> !> Best regards,
    > > !!!> !> Yanhong Huang
    > > !!!> !> Microsoft Online Partner Support
    > > !!!> !>
    > > !!!> !> Get Secure! - www.microsoft.com/security
    > > !!!> !> This posting is provided "AS IS" with no warranties, and confers

    > no
    > > !!!> !rights.
    > > !!!> !>
    > > !!!> !> --------------------
    > > !!!> !> !Content-Class: urn:content-classes:message
    > > !!!> !> !From: "Joel Zhou" <>
    > > !!!> !> !Sender: "Joel Zhou" <>
    > > !!!> !> !Subject: "The operation has timed-out." exception on WinXP
    > > !!!> !> !Date: Wed, 16 Jul 2003 16:03:59 -0700
    > > !!!> !> !Lines: 39
    > > !!!> !> !Message-ID: <05e601c34bee$8a519d50$>
    > > !!!> !> !MIME-Version: 1.0
    > > !!!> !> !Content-Type: text/plain;
    > > !!!> !> ! charset="iso-8859-1"
    > > !!!> !> !Content-Transfer-Encoding: 7bit
    > > !!!> !> !X-Newsreader: Microsoft CDO for Windows 2000
    > > !!!> !> !X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    > > !!!> !> !Thread-Index: AcNL7opR4m2aDJgCSfSToDfa2GQ+3A==
    > > !!!> !> !Newsgroups:

    microsoft.public.dotnet.framework.aspnet.webservices
    > > !!!> !> !Path: cpmsftngxa06.phx.gbl
    > > !!!> !> !Xref: cpmsftngxa06.phx.gbl
    > > !!!> !microsoft.public.dotnet.framework.aspnet.webservices:18319
    > > !!!> !> !NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    > > !!!> !> !X-Tomcat-NG:

    microsoft.public.dotnet.framework.aspnet.webservices
    > > !!!> !> !
    > > !!!> !> !Our web clients makes synchronous web method calls to a
    > > !!!> !> !web service on a XP workstation, running .Net 1.1.4322.
    > > !!!> !> !
    > > !!!> !> !When there are already 10 connections to the IIS, the
    > > !!!> !> !client gets "The request failed with HTTP status 403:
    > > !!!> !> !Access Forbidden." when calling the web service. This is
    > > !!!> !> !expected behavior documented by MSDN. However, my problem
    > > !!!> !> !is if the client (same thread) tries to make the call
    > > !!!> !> !again after the total connection < 10, it will get "The
    > > !!!> !> !operation has timed-out." exception first, and then if the
    > > !!!> !> !client makes the same call again, it will work.
    > > !!!> !> !
    > > !!!> !> !If the IIS connection stays at 10, the client will get
    > > !!!> !> !those two exceptions one after another. I am expecting the
    > > !!!> !> !client to always get the "..Access Forbidden" exception.
    > > !!!> !> !
    > > !!!> !> !It seems that after the "...403: Access Forbidden" error,
    > > !!!> !> !the client will always get a "The operation has timed-
    > > !!!> !> !out." before it will work again. I set the client side
    > > !!!> !> !timeout to 30 seconds. The timeout exception happens about
    > > !!!> !> !90 seconds after making the call.
    > > !!!> !> !
    > > !!!> !> !I am trying to figure out how to avoid the timeout
    > > !!!> !> !exception. Any suggestions?
    > > !!!> !> !
    > > !!!> !> !The exception call stack is below:
    > > !!!> !> !Error: System.Net.WebException: The operation has timed-
    > > !!!> !> !out.
    > > !!!> !> ! at System.Net.HttpWebRequest.GetRequestStream()
    > > !!!> !> ! at
    > > !!!> !> !System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    > > !!!> !> !(String methodN
    > > !!!> !> !ame, Object[] parameters)
    > > !!!> !> ! at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    > > !!!> !> !methodName, Object[] p
    > > !!!> !> !arameters) in
    > > !!!> !> !d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    > > !!!> !> !:line 3
    > > !!!> !> !
    > > !!!> !> !
    > > !!!> !>
    > > !!!> !>
    > > !!!> !
    > > !!!> !
    > > !!!> !
    > > !!!>
    > > !!!>
    > > !!!
    > > !!!
    > > !!!
    > > !!
    > > !!
    > > !!
    > > !
    > > !
    > > !
    > >
    > >

    >
    >
    Joel Zhou, Jul 31, 2003
    #12
  13. Glad to hear it. Maybe you added some patch/update during these days.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !From: (Daniel Buchholz)
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !Date: Thu, 31 Jul 2003 09:31:45 GMT
    !Lines: 19
    !Message-ID: <>
    !References: <05e601c34bee$8a519d50$> <>
    <#> <> <#sD2G3UUDHA.2368
    @TK2MSFTNGP09.phx.gbl> <Lln$> <>
    <> <>
    !NNTP-Posting-Host: 145.228.10.180
    !X-Trace: news.uni-berlin.de 1059643906 24082020 145.228.10.180 (16 [53906])
    !X-Newsreader: Forte Free Agent 1.21/32.243
    !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!fu-
    berlin.de!uni-berlin.de!145.228.10.180!not-for-mail
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18557
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !
    !On Thu, 31 Jul 2003 08:10:07 GMT,
    !(Yan-Hong Huang[MSFT]) wrote:
    !
    !>Hi Daniel,
    !>
    !>Have you tried to enlarge connections in connectionManagement in machine.config?
    !>
    !
    !Yes, we did that and it helped only a little.
    !
    !Figured out in the last hour that we forgot to explicitly Close() the
    !WebResponse object. Then the problems are gone. Without the call to
    !Close the connections remain in the state CLOSE_WAIT in the output of
    !netstat.
    !
    !Strange, as the application worked fine over the last days without the
    !call to Close().
    !
    !Daniel
    !
    Yan-Hong Huang[MSFT], Aug 1, 2003
    #13
  14. Joel Zhou

    Pica Guest

    Thx for your reply Yanhong.

    If thats the only workaround, I have a big problem since our software has to
    be rolled out on a win2k server.

    Our customer needs mimimum 12 months before authorisation of this upgrade
    (Win2k to win2003)can occur. The software has to go live in bout 1 month.

    Is there ANY other known workaround for this problem?

    1. One option would be to use html pages with javascript to consume the
    webservices, since consuming webservices on the same server works without
    any problems. Due to complexity I need to implement *.aspx pages though.

    Any tips??



    "Yan-Hong Huang[MSFT]" <> schrieb im Newsbeitrag
    news:...
    > Hello,
    >
    > Based on our testing and discussion here, it is resolved after you

    installed VS.NET 2003 and Framework 1.1.
    >
    > Thanks.
    >
    > Best regards,
    > Yanhong Huang
    > Microsoft Online Partner Support
    >
    > Get Secure! - www.microsoft.com/security
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    >
    > --------------------
    > !From: "Pica" <>
    > !References: <05e601c34bee$8a519d50$>
    > !Subject: Re: "The operation has timed-out." exception on WinXP
    > !Date: Mon, 4 Aug 2003 11:15:33 +0200
    > !Lines: 60
    > !X-Priority: 3
    > !X-MSMail-Priority: Normal
    > !X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
    > !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
    > !Message-ID: <>
    > !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !NNTP-Posting-Host: 213.83.44.106
    > !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
    > !Xref: cpmsftngxa06.phx.gbl

    microsoft.public.dotnet.framework.aspnet.webservices:18607
    > !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !
    > !Hi Joel,
    > !
    > !did you solve this problem yet?
    > !
    > !I have a similiar timeout problem when I call my webservice in a web
    > !application.
    > !
    > !Sometimes it works and sometimes not at all. All VB versions of this
    > !application work, just not the web version of it.
    > !If I the web application and web service are on different machines

    (win2k)
    > !the web application works perfectly.
    > !
    > !Thx in advance.
    > !
    > !
    > !
    > !
    > !"Joel Zhou" <> schrieb im Newsbeitrag
    > !news:05e601c34bee$8a519d50$...
    > !> Our web clients makes synchronous web method calls to a
    > !> web service on a XP workstation, running .Net 1.1.4322.
    > !>
    > !> When there are already 10 connections to the IIS, the
    > !> client gets "The request failed with HTTP status 403:
    > !> Access Forbidden." when calling the web service. This is
    > !> expected behavior documented by MSDN. However, my problem
    > !> is if the client (same thread) tries to make the call
    > !> again after the total connection < 10, it will get "The
    > !> operation has timed-out." exception first, and then if the
    > !> client makes the same call again, it will work.
    > !>
    > !> If the IIS connection stays at 10, the client will get
    > !> those two exceptions one after another. I am expecting the
    > !> client to always get the "..Access Forbidden" exception.
    > !>
    > !> It seems that after the "...403: Access Forbidden" error,
    > !> the client will always get a "The operation has timed-
    > !> out." before it will work again. I set the client side
    > !> timeout to 30 seconds. The timeout exception happens about
    > !> 90 seconds after making the call.
    > !>
    > !> I am trying to figure out how to avoid the timeout
    > !> exception. Any suggestions?
    > !>
    > !> The exception call stack is below:
    > !> Error: System.Net.WebException: The operation has timed-
    > !> out.
    > !> at System.Net.HttpWebRequest.GetRequestStream()
    > !> at
    > !> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    > !> (String methodN
    > !> ame, Object[] parameters)
    > !> at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    > !> methodName, Object[] p
    > !> arameters) in
    > !> d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    > !> :line 3
    > !>
    > !
    > !
    > !
    >
    >
    Pica, Aug 5, 2003
    #14
  15. Hello Pica,

    This problem is only related to .NET framework ( not OS). So please install .NET framwork 1.1 version on the system. When
    developing the web applicaiton, use VS.NET 2003.

    Thanks.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !From: "Pica" <>
    !References: <05e601c34bee$8a519d50$> <>
    <>
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !Date: Tue, 5 Aug 2003 10:50:31 +0200
    !Lines: 119
    !X-Priority: 3
    !X-MSMail-Priority: Normal
    !X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
    !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
    !Message-ID: <#>
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !NNTP-Posting-Host: 213.83.44.106
    !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.webservices:18631
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !
    !Thx for your reply Yanhong.
    !
    !If thats the only workaround, I have a big problem since our software has to
    !be rolled out on a win2k server.
    !
    !Our customer needs mimimum 12 months before authorisation of this upgrade
    !(Win2k to win2003)can occur. The software has to go live in bout 1 month.
    !
    !Is there ANY other known workaround for this problem?
    !
    !1. One option would be to use html pages with javascript to consume the
    !webservices, since consuming webservices on the same server works without
    !any problems. Due to complexity I need to implement *.aspx pages though.
    !
    !Any tips??
    !
    !
    !
    !"Yan-Hong Huang[MSFT]" <> schrieb im Newsbeitrag
    !news:...
    !> Hello,
    !>
    !> Based on our testing and discussion here, it is resolved after you
    !installed VS.NET 2003 and Framework 1.1.
    !>
    !> Thanks.
    !>
    !> Best regards,
    !> Yanhong Huang
    !> Microsoft Online Partner Support
    !>
    !> Get Secure! - www.microsoft.com/security
    !> This posting is provided "AS IS" with no warranties, and confers no
    !rights.
    !>
    !> --------------------
    !> !From: "Pica" <>
    !> !References: <05e601c34bee$8a519d50$>
    !> !Subject: Re: "The operation has timed-out." exception on WinXP
    !> !Date: Mon, 4 Aug 2003 11:15:33 +0200
    !> !Lines: 60
    !> !X-Priority: 3
    !> !X-MSMail-Priority: Normal
    !> !X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
    !> !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
    !> !Message-ID: <>
    !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !> !NNTP-Posting-Host: 213.83.44.106
    !> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
    !> !Xref: cpmsftngxa06.phx.gbl
    !microsoft.public.dotnet.framework.aspnet.webservices:18607
    !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !> !
    !> !Hi Joel,
    !> !
    !> !did you solve this problem yet?
    !> !
    !> !I have a similiar timeout problem when I call my webservice in a web
    !> !application.
    !> !
    !> !Sometimes it works and sometimes not at all. All VB versions of this
    !> !application work, just not the web version of it.
    !> !If I the web application and web service are on different machines
    !(win2k)
    !> !the web application works perfectly.
    !> !
    !> !Thx in advance.
    !> !
    !> !
    !> !
    !> !
    !> !"Joel Zhou" <> schrieb im Newsbeitrag
    !> !news:05e601c34bee$8a519d50$...
    !> !> Our web clients makes synchronous web method calls to a
    !> !> web service on a XP workstation, running .Net 1.1.4322.
    !> !>
    !> !> When there are already 10 connections to the IIS, the
    !> !> client gets "The request failed with HTTP status 403:
    !> !> Access Forbidden." when calling the web service. This is
    !> !> expected behavior documented by MSDN. However, my problem
    !> !> is if the client (same thread) tries to make the call
    !> !> again after the total connection < 10, it will get "The
    !> !> operation has timed-out." exception first, and then if the
    !> !> client makes the same call again, it will work.
    !> !>
    !> !> If the IIS connection stays at 10, the client will get
    !> !> those two exceptions one after another. I am expecting the
    !> !> client to always get the "..Access Forbidden" exception.
    !> !>
    !> !> It seems that after the "...403: Access Forbidden" error,
    !> !> the client will always get a "The operation has timed-
    !> !> out." before it will work again. I set the client side
    !> !> timeout to 30 seconds. The timeout exception happens about
    !> !> 90 seconds after making the call.
    !> !>
    !> !> I am trying to figure out how to avoid the timeout
    !> !> exception. Any suggestions?
    !> !>
    !> !> The exception call stack is below:
    !> !> Error: System.Net.WebException: The operation has timed-
    !> !> out.
    !> !> at System.Net.HttpWebRequest.GetRequestStream()
    !> !> at
    !> !> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    !> !> (String methodN
    !> !> ame, Object[] parameters)
    !> !> at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    !> !> methodName, Object[] p
    !> !> arameters) in
    !> !> d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    !> !> :line 3
    !> !>
    !> !
    !> !
    !> !
    !>
    !>
    !
    !
    !
    Yan-Hong Huang[MSFT], Aug 5, 2003
    #15
  16. Joel Zhou

    Pica Guest

    Awesome, thx Yanhong,

    somehow I assumed I need the 2003 Server too. I'll test it.

    Have a nice day :)



    "Yan-Hong Huang[MSFT]" <> schrieb im Newsbeitrag
    news:...
    > Hello Pica,
    >
    > This problem is only related to .NET framework ( not OS). So please

    install .NET framwork 1.1 version on the system. When
    > developing the web applicaiton, use VS.NET 2003.
    >
    > Thanks.
    >
    > Best regards,
    > Yanhong Huang
    > Microsoft Online Partner Support
    >
    > Get Secure! - www.microsoft.com/security
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    >
    > --------------------
    > !From: "Pica" <>
    > !References: <05e601c34bee$8a519d50$>

    <>
    > <>
    > !Subject: Re: "The operation has timed-out." exception on WinXP
    > !Date: Tue, 5 Aug 2003 10:50:31 +0200
    > !Lines: 119
    > !X-Priority: 3
    > !X-MSMail-Priority: Normal
    > !X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
    > !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
    > !Message-ID: <#>
    > !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !NNTP-Posting-Host: 213.83.44.106
    > !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
    > !Xref: cpmsftngxa06.phx.gbl

    microsoft.public.dotnet.framework.aspnet.webservices:18631
    > !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !
    > !Thx for your reply Yanhong.
    > !
    > !If thats the only workaround, I have a big problem since our software has

    to
    > !be rolled out on a win2k server.
    > !
    > !Our customer needs mimimum 12 months before authorisation of this upgrade
    > !(Win2k to win2003)can occur. The software has to go live in bout 1 month.
    > !
    > !Is there ANY other known workaround for this problem?
    > !
    > !1. One option would be to use html pages with javascript to consume the
    > !webservices, since consuming webservices on the same server works without
    > !any problems. Due to complexity I need to implement *.aspx pages though.
    > !
    > !Any tips??
    > !
    > !
    > !
    > !"Yan-Hong Huang[MSFT]" <> schrieb im

    Newsbeitrag
    > !news:...
    > !> Hello,
    > !>
    > !> Based on our testing and discussion here, it is resolved after you
    > !installed VS.NET 2003 and Framework 1.1.
    > !>
    > !> Thanks.
    > !>
    > !> Best regards,
    > !> Yanhong Huang
    > !> Microsoft Online Partner Support
    > !>
    > !> Get Secure! - www.microsoft.com/security
    > !> This posting is provided "AS IS" with no warranties, and confers no
    > !rights.
    > !>
    > !> --------------------
    > !> !From: "Pica" <>
    > !> !References: <05e601c34bee$8a519d50$>
    > !> !Subject: Re: "The operation has timed-out." exception on WinXP
    > !> !Date: Mon, 4 Aug 2003 11:15:33 +0200
    > !> !Lines: 60
    > !> !X-Priority: 3
    > !> !X-MSMail-Priority: Normal
    > !> !X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
    > !> !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
    > !> !Message-ID: <>
    > !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !> !NNTP-Posting-Host: 213.83.44.106
    > !> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
    > !> !Xref: cpmsftngxa06.phx.gbl
    > !microsoft.public.dotnet.framework.aspnet.webservices:18607
    > !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !> !
    > !> !Hi Joel,
    > !> !
    > !> !did you solve this problem yet?
    > !> !
    > !> !I have a similiar timeout problem when I call my webservice in a web
    > !> !application.
    > !> !
    > !> !Sometimes it works and sometimes not at all. All VB versions of this
    > !> !application work, just not the web version of it.
    > !> !If I the web application and web service are on different machines
    > !(win2k)
    > !> !the web application works perfectly.
    > !> !
    > !> !Thx in advance.
    > !> !
    > !> !
    > !> !
    > !> !
    > !> !"Joel Zhou" <> schrieb im Newsbeitrag
    > !> !news:05e601c34bee$8a519d50$...
    > !> !> Our web clients makes synchronous web method calls to a
    > !> !> web service on a XP workstation, running .Net 1.1.4322.
    > !> !>
    > !> !> When there are already 10 connections to the IIS, the
    > !> !> client gets "The request failed with HTTP status 403:
    > !> !> Access Forbidden." when calling the web service. This is
    > !> !> expected behavior documented by MSDN. However, my problem
    > !> !> is if the client (same thread) tries to make the call
    > !> !> again after the total connection < 10, it will get "The
    > !> !> operation has timed-out." exception first, and then if the
    > !> !> client makes the same call again, it will work.
    > !> !>
    > !> !> If the IIS connection stays at 10, the client will get
    > !> !> those two exceptions one after another. I am expecting the
    > !> !> client to always get the "..Access Forbidden" exception.
    > !> !>
    > !> !> It seems that after the "...403: Access Forbidden" error,
    > !> !> the client will always get a "The operation has timed-
    > !> !> out." before it will work again. I set the client side
    > !> !> timeout to 30 seconds. The timeout exception happens about
    > !> !> 90 seconds after making the call.
    > !> !>
    > !> !> I am trying to figure out how to avoid the timeout
    > !> !> exception. Any suggestions?
    > !> !>
    > !> !> The exception call stack is below:
    > !> !> Error: System.Net.WebException: The operation has timed-
    > !> !> out.
    > !> !> at System.Net.HttpWebRequest.GetRequestStream()
    > !> !> at
    > !> !> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
    > !> !> (String methodN
    > !> !> ame, Object[] parameters)
    > !> !> at EasyIt_SDK.EasySoapHttpClientProtocol.Invoke(String
    > !> !> methodName, Object[] p
    > !> !> arameters) in
    > !> !> d:\easyit\code\src\easyit_sdk\easysoaphttpclientprotocol.cs
    > !> !> :line 3
    > !> !>
    > !> !
    > !> !
    > !> !
    > !>
    > !>
    > !
    > !
    > !
    >
    >
    Pica, Aug 5, 2003
    #16
  17. Joel Zhou

    Ramana Guest

    Hi,
    I am facing a similar ptoblem but wirh soap request.

    Here are the problem details. I am in deep trouble. Please help me fixing
    the problem.


    I am building a Windows Forms application to consume Webservices provided

    by the jboss server. I used the Windows WSDL.exe tool to generate the proxy

    code. The proxy code file has been added to my windows forms aplication.

    When the exposed webservice methods are called, application gives the timed

    out error("The operation has timed-out."). There is no proxy between the

    client and server.

    We checked that the server is sending response properly but the my

    webrequest is unable to recieve the response.

    This problem is happening after working for some time not every time.

    However, once this problem comes, I am not able to run the same

    application on any machine but other users are able to run the same

    application on the same machine. With this, we assumed that my roaming

    profile got corrupted and restored some old profile then I am able to run

    the application again. The same thing happend to many of my team members

    also.

    I think profile corruption is very dangerous and we need some urgent

    solution for this before rolling my application to actual users.

    Advace Thanks

    Ramana



    Here is the code snippet:

    //Web Service method called like below

    ClientConfigLocalService ccls = new ClientConfigLocalService();

    string xmlConfig = ccls.getURLs("4545454");



    //ClientConfigLocalService.CS (WSDL tool generated file)

    //-------------------------------------------------------------------------

    -

    ----

    // <autogenerated>

    // This code was generated by a tool.

    // Runtime Version: 1.0.3705.0

    //

    // Changes to this file may cause incorrect behavior and will be lost

    if

    // the code is regenerated.

    // </autogenerated>

    //-------------------------------------------------------------------------

    -

    ----

    //

    // This source code was auto-generated by wsdl, Version=1.0.3705.0.

    //

    using System.Diagnostics;

    using System.Xml.Serialization;

    using System;

    using System.Web.Services.Protocols;

    using System.ComponentModel;

    using System.Web.Services;



    /// <remarks/>

    [System.Diagnostics.DebuggerStepThroughAttribute()]

    [System.ComponentModel.DesignerCategoryAttribute("code")]

    [System.Web.Services.WebServiceBindingAttribute

    (Name="CasClientConfigSoapBin

    ding",

    Namespace="http://mycompany.com:8080/jboss-net/services/CasClientCo

    nfig")]

    public class ClientConfigLocalService :

    System.Web.Services.Protocols.SoapHttpClientProtocol {

    /// <remarks/>

    public ClientConfigLocalService() {

    this.Url =

    "http://mycompany.com:8080/jboss-net/services/CasClientConfig";

    }

    /// <remarks/>

    [System.Web.Services.Protocols.SoapRpcMethodAttribute

    ("CasClientConfig",

    RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC

    lientConfig",

    ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas

    ClientConfig")]

    [return: System.Xml.Serialization.SoapElementAttribute

    ("getURLsReturn")]

    public string getURLs(string in0) {

    object[] results = this.Invoke("getURLs", new object[] {

    in0});

    return ((string)(results[0]));

    }

    /// <remarks/>

    public System.IAsyncResult BegingetURLs(string in0,

    System.AsyncCallback

    callback, object asyncState) {

    return this.BeginInvoke("getURLs", new object[] {

    in0}, callback, asyncState);

    }

    /// <remarks/>

    public string EndgetURLs(System.IAsyncResult asyncResult) {

    object[] results = this.EndInvoke(asyncResult);

    return ((string)(results[0]));

    }

    /// <remarks/>

    [System.Web.Services.Protocols.SoapRpcMethodAttribute

    ("CasClientConfig",

    RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC

    lientConfig",

    ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas

    ClientConfig")]

    [return:

    System.Xml.Serialization.SoapElementAttribute("getServerVersionReturn")]

    public string getServerVersion() {

    object[] results = this.Invoke("getServerVersion", new object[0]);

    return ((string)(results[0]));

    }

    /// <remarks/>

    public System.IAsyncResult BegingetServerVersion(System.AsyncCallback

    callback, object asyncState) {

    return this.BeginInvoke("getServerVersion", new object[0],

    callback,

    asyncState);

    }

    /// <remarks/>

    public string EndgetServerVersion(System.IAsyncResult asyncResult) {

    object[] results = this.EndInvoke(asyncResult);

    return ((string)(results[0]));

    }

    /// <remarks/>

    [System.Web.Services.Protocols.SoapRpcMethodAttribute

    ("CasClientConfig",

    RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC

    lientConfig",

    ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas

    ClientConfig")]

    [return:

    System.Xml.Serialization.SoapElementAttribute("getObjectConfigReturn")]

    public string getObjectConfig(string in0) {

    object[] results = this.Invoke("getObjectConfig", new object[] {

    in0});

    return ((string)(results[0]));

    }

    /// <remarks/>

    public System.IAsyncResult BegingetObjectConfig(string in0,

    System.AsyncCallback callback, object asyncState) {

    return this.BeginInvoke("getObjectConfig", new object[] {

    in0}, callback, asyncState);

    }

    /// <remarks/>

    public string EndgetObjectConfig(System.IAsyncResult asyncResult) {

    object[] results = this.EndInvoke(asyncResult);

    return ((string)(results[0]));

    }

    }
    Ramana, Sep 25, 2003
    #17
  18. Hello Ramana,

    Thanks for posting in the group.

    Here is some suggestions for you:

    1) If you create web reference in .NET IDE, will u meet it?

    2) Please correct to other web services to see if the problem is there?

    3) Use SoapTrace tool in soap toolkit to compare the difference of soap
    message.

    If you still can't find out the reason, I suggest you contact Microsoft
    Product Support Service in order that a support professional will work with
    you specially on this problem. Here is the link for your reference:
    http://support.microsoft.com/common/international.aspx?rdpath=fh;en-us;cntac
    tms

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !From: "Ramana" <>
    !References: <05e601c34bee$8a519d50$>
    <>
    <>
    <#>
    <>
    <>
    <uBr$pg$>
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !Date: Thu, 25 Sep 2003 16:33:20 +0530
    !Lines: 294
    !X-Priority: 3
    !X-MSMail-Priority: Normal
    !X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
    !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
    !Message-ID: <>
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !NNTP-Posting-Host: skater.hyd.deshaw.com 149.77.163.156
    !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl
    microsoft.public.dotnet.framework.aspnet.webservices:19534
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !
    !Hi,
    !I am facing a similar ptoblem but wirh soap request.
    !
    !Here are the problem details. I am in deep trouble. Please help me fixing
    !the problem.
    !
    !
    !I am building a Windows Forms application to consume Webservices provided
    !
    !by the jboss server. I used the Windows WSDL.exe tool to generate the proxy
    !
    !code. The proxy code file has been added to my windows forms aplication.
    !
    !When the exposed webservice methods are called, application gives the timed
    !
    !out error("The operation has timed-out."). There is no proxy between the
    !
    !client and server.
    !
    !We checked that the server is sending response properly but the my
    !
    !webrequest is unable to recieve the response.
    !
    !This problem is happening after working for some time not every time.
    !
    !However, once this problem comes, I am not able to run the same
    !
    !application on any machine but other users are able to run the same
    !
    !application on the same machine. With this, we assumed that my roaming
    !
    !profile got corrupted and restored some old profile then I am able to run
    !
    !the application again. The same thing happend to many of my team members
    !
    !also.
    !
    !I think profile corruption is very dangerous and we need some urgent
    !
    !solution for this before rolling my application to actual users.
    !
    !Advace Thanks
    !
    !Ramana
    !
    !
    !
    !Here is the code snippet:
    !
    !//Web Service method called like below
    !
    !ClientConfigLocalService ccls = new ClientConfigLocalService();
    !
    !string xmlConfig = ccls.getURLs("4545454");
    !
    !
    !
    !//ClientConfigLocalService.CS (WSDL tool generated file)
    !
    !//-------------------------------------------------------------------------
    !
    !-
    !
    !----
    !
    !// <autogenerated>
    !
    !// This code was generated by a tool.
    !
    !// Runtime Version: 1.0.3705.0
    !
    !//
    !
    !// Changes to this file may cause incorrect behavior and will be lost
    !
    !if
    !
    !// the code is regenerated.
    !
    !// </autogenerated>
    !
    !//-------------------------------------------------------------------------
    !
    !-
    !
    !----
    !
    !//
    !
    !// This source code was auto-generated by wsdl, Version=1.0.3705.0.
    !
    !//
    !
    !using System.Diagnostics;
    !
    !using System.Xml.Serialization;
    !
    !using System;
    !
    !using System.Web.Services.Protocols;
    !
    !using System.ComponentModel;
    !
    !using System.Web.Services;
    !
    !
    !
    !/// <remarks/>
    !
    ![System.Diagnostics.DebuggerStepThroughAttribute()]
    !
    ![System.ComponentModel.DesignerCategoryAttribute("code")]
    !
    ![System.Web.Services.WebServiceBindingAttribute
    !
    !(Name="CasClientConfigSoapBin
    !
    !ding",
    !
    !Namespace="http://mycompany.com:8080/jboss-net/services/CasClientCo
    !
    !nfig")]
    !
    !public class ClientConfigLocalService :
    !
    !System.Web.Services.Protocols.SoapHttpClientProtocol {
    !
    !/// <remarks/>
    !
    !public ClientConfigLocalService() {
    !
    !this.Url =
    !
    !"http://mycompany.com:8080/jboss-net/services/CasClientConfig";
    !
    !}
    !
    !/// <remarks/>
    !
    ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    !
    !("CasClientConfig",
    !
    !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    !
    !lientConfig",
    !
    !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    !
    !ClientConfig")]
    !
    ![return: System.Xml.Serialization.SoapElementAttribute
    !
    !("getURLsReturn")]
    !
    !public string getURLs(string in0) {
    !
    !object[] results = this.Invoke("getURLs", new object[] {
    !
    !in0});
    !
    !return ((string)(results[0]));
    !
    !}
    !
    !/// <remarks/>
    !
    !public System.IAsyncResult BegingetURLs(string in0,
    !
    !System.AsyncCallback
    !
    !callback, object asyncState) {
    !
    !return this.BeginInvoke("getURLs", new object[] {
    !
    !in0}, callback, asyncState);
    !
    !}
    !
    !/// <remarks/>
    !
    !public string EndgetURLs(System.IAsyncResult asyncResult) {
    !
    !object[] results = this.EndInvoke(asyncResult);
    !
    !return ((string)(results[0]));
    !
    !}
    !
    !/// <remarks/>
    !
    ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    !
    !("CasClientConfig",
    !
    !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    !
    !lientConfig",
    !
    !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    !
    !ClientConfig")]
    !
    ![return:
    !
    !System.Xml.Serialization.SoapElementAttribute("getServerVersionReturn")]
    !
    !public string getServerVersion() {
    !
    !object[] results = this.Invoke("getServerVersion", new object[0]);
    !
    !return ((string)(results[0]));
    !
    !}
    !
    !/// <remarks/>
    !
    !public System.IAsyncResult BegingetServerVersion(System.AsyncCallback
    !
    !callback, object asyncState) {
    !
    !return this.BeginInvoke("getServerVersion", new object[0],
    !
    !callback,
    !
    !asyncState);
    !
    !}
    !
    !/// <remarks/>
    !
    !public string EndgetServerVersion(System.IAsyncResult asyncResult) {
    !
    !object[] results = this.EndInvoke(asyncResult);
    !
    !return ((string)(results[0]));
    !
    !}
    !
    !/// <remarks/>
    !
    ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    !
    !("CasClientConfig",
    !
    !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    !
    !lientConfig",
    !
    !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    !
    !ClientConfig")]
    !
    ![return:
    !
    !System.Xml.Serialization.SoapElementAttribute("getObjectConfigReturn")]
    !
    !public string getObjectConfig(string in0) {
    !
    !object[] results = this.Invoke("getObjectConfig", new object[] {
    !
    !in0});
    !
    !return ((string)(results[0]));
    !
    !}
    !
    !/// <remarks/>
    !
    !public System.IAsyncResult BegingetObjectConfig(string in0,
    !
    !System.AsyncCallback callback, object asyncState) {
    !
    !return this.BeginInvoke("getObjectConfig", new object[] {
    !
    !in0}, callback, asyncState);
    !
    !}
    !
    !/// <remarks/>
    !
    !public string EndgetObjectConfig(System.IAsyncResult asyncResult) {
    !
    !object[] results = this.EndInvoke(asyncResult);
    !
    !return ((string)(results[0]));
    !
    !}
    !
    !}
    !
    !
    !
    !
    !
    Yan-Hong Huang[MSFT], Sep 26, 2003
    #18
  19. Joel Zhou

    Ramana Guest

    Hi Yanhong Huang,

    Thanks for the reply.

    I am able to consume other web services created by ASP.NET and the WSDL
    generated for ASP webservice and jboss web service are identical.
    I did some expernimentation with the problamatic profile and found yesterday
    evening that a registry key is creating the problem
    Here is the key
    ([HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
    Settings\Connections]\DefaultConnectionSettings)
    I think SOAP is using the default proxy settings available in the user
    profile. The application is working after removing this key. We also found
    another fix by setting the proxy preoperty of soap object to 'empty proxy'
    and found the program working fine. We are going to apply this solution in
    our project.
    However, I could not find how (and Which programe changed the key) this
    registry key is changed to a particular user.

    Any idea on this will help us to document the problem more clearly so taht
    other teams will not face a similar problem.

    Thanks,
    Ramana


    "Yan-Hong Huang[MSFT]" <> wrote in message
    news:n70ERa$...
    > Hello Ramana,
    >
    > Thanks for posting in the group.
    >
    > Here is some suggestions for you:
    >
    > 1) If you create web reference in .NET IDE, will u meet it?
    >
    > 2) Please correct to other web services to see if the problem is there?
    >
    > 3) Use SoapTrace tool in soap toolkit to compare the difference of soap
    > message.
    >
    > If you still can't find out the reason, I suggest you contact Microsoft
    > Product Support Service in order that a support professional will work

    with
    > you specially on this problem. Here is the link for your reference:
    >

    http://support.microsoft.com/common/international.aspx?rdpath=fh;en-us;cntac
    > tms
    >
    > Best regards,
    > Yanhong Huang
    > Microsoft Online Partner Support
    >
    > Get Secure! - www.microsoft.com/security
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    >
    > --------------------
    > !From: "Ramana" <>
    > !References: <05e601c34bee$8a519d50$>
    > <>
    > <>
    > <#>
    > <>
    > <>
    > <uBr$pg$>
    > !Subject: Re: "The operation has timed-out." exception on WinXP
    > !Date: Thu, 25 Sep 2003 16:33:20 +0530
    > !Lines: 294
    > !X-Priority: 3
    > !X-MSMail-Priority: Normal
    > !X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
    > !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
    > !Message-ID: <>
    > !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    > !NNTP-Posting-Host: skater.hyd.deshaw.com 149.77.163.156
    > !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
    > !Xref: cpmsftngxa06.phx.gbl
    > microsoft.public.dotnet.framework.aspnet.webservices:19534
    > !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    > !
    > !Hi,
    > !I am facing a similar ptoblem but wirh soap request.
    > !
    > !Here are the problem details. I am in deep trouble. Please help me fixing
    > !the problem.
    > !
    > !
    > !I am building a Windows Forms application to consume Webservices provided
    > !
    > !by the jboss server. I used the Windows WSDL.exe tool to generate the

    proxy
    > !
    > !code. The proxy code file has been added to my windows forms aplication.
    > !
    > !When the exposed webservice methods are called, application gives the

    timed
    > !
    > !out error("The operation has timed-out."). There is no proxy between the
    > !
    > !client and server.
    > !
    > !We checked that the server is sending response properly but the my
    > !
    > !webrequest is unable to recieve the response.
    > !
    > !This problem is happening after working for some time not every time.
    > !
    > !However, once this problem comes, I am not able to run the same
    > !
    > !application on any machine but other users are able to run the same
    > !
    > !application on the same machine. With this, we assumed that my roaming
    > !
    > !profile got corrupted and restored some old profile then I am able to run
    > !
    > !the application again. The same thing happend to many of my team members
    > !
    > !also.
    > !
    > !I think profile corruption is very dangerous and we need some urgent
    > !
    > !solution for this before rolling my application to actual users.
    > !
    > !Advace Thanks
    > !
    > !Ramana
    > !
    > !
    > !
    > !Here is the code snippet:
    > !
    > !//Web Service method called like below
    > !
    > !ClientConfigLocalService ccls = new ClientConfigLocalService();
    > !
    > !string xmlConfig = ccls.getURLs("4545454");
    > !
    > !
    > !
    > !//ClientConfigLocalService.CS (WSDL tool generated file)
    > !
    >

    !//-------------------------------------------------------------------------
    > !
    > !-
    > !
    > !----
    > !
    > !// <autogenerated>
    > !
    > !// This code was generated by a tool.
    > !
    > !// Runtime Version: 1.0.3705.0
    > !
    > !//
    > !
    > !// Changes to this file may cause incorrect behavior and will be lost
    > !
    > !if
    > !
    > !// the code is regenerated.
    > !
    > !// </autogenerated>
    > !
    >

    !//-------------------------------------------------------------------------
    > !
    > !-
    > !
    > !----
    > !
    > !//
    > !
    > !// This source code was auto-generated by wsdl, Version=1.0.3705.0.
    > !
    > !//
    > !
    > !using System.Diagnostics;
    > !
    > !using System.Xml.Serialization;
    > !
    > !using System;
    > !
    > !using System.Web.Services.Protocols;
    > !
    > !using System.ComponentModel;
    > !
    > !using System.Web.Services;
    > !
    > !
    > !
    > !/// <remarks/>
    > !
    > ![System.Diagnostics.DebuggerStepThroughAttribute()]
    > !
    > ![System.ComponentModel.DesignerCategoryAttribute("code")]
    > !
    > ![System.Web.Services.WebServiceBindingAttribute
    > !
    > !(Name="CasClientConfigSoapBin
    > !
    > !ding",
    > !
    > !Namespace="http://mycompany.com:8080/jboss-net/services/CasClientCo
    > !
    > !nfig")]
    > !
    > !public class ClientConfigLocalService :
    > !
    > !System.Web.Services.Protocols.SoapHttpClientProtocol {
    > !
    > !/// <remarks/>
    > !
    > !public ClientConfigLocalService() {
    > !
    > !this.Url =
    > !
    > !"http://mycompany.com:8080/jboss-net/services/CasClientConfig";
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    > !
    > !("CasClientConfig",
    > !
    > !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    > !
    > !lientConfig",
    > !
    > !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    > !
    > !ClientConfig")]
    > !
    > ![return: System.Xml.Serialization.SoapElementAttribute
    > !
    > !("getURLsReturn")]
    > !
    > !public string getURLs(string in0) {
    > !
    > !object[] results = this.Invoke("getURLs", new object[] {
    > !
    > !in0});
    > !
    > !return ((string)(results[0]));
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > !public System.IAsyncResult BegingetURLs(string in0,
    > !
    > !System.AsyncCallback
    > !
    > !callback, object asyncState) {
    > !
    > !return this.BeginInvoke("getURLs", new object[] {
    > !
    > !in0}, callback, asyncState);
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > !public string EndgetURLs(System.IAsyncResult asyncResult) {
    > !
    > !object[] results = this.EndInvoke(asyncResult);
    > !
    > !return ((string)(results[0]));
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    > !
    > !("CasClientConfig",
    > !
    > !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    > !
    > !lientConfig",
    > !
    > !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    > !
    > !ClientConfig")]
    > !
    > ![return:
    > !
    > !System.Xml.Serialization.SoapElementAttribute("getServerVersionReturn")]
    > !
    > !public string getServerVersion() {
    > !
    > !object[] results = this.Invoke("getServerVersion", new object[0]);
    > !
    > !return ((string)(results[0]));
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > !public System.IAsyncResult BegingetServerVersion(System.AsyncCallback
    > !
    > !callback, object asyncState) {
    > !
    > !return this.BeginInvoke("getServerVersion", new object[0],
    > !
    > !callback,
    > !
    > !asyncState);
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > !public string EndgetServerVersion(System.IAsyncResult asyncResult) {
    > !
    > !object[] results = this.EndInvoke(asyncResult);
    > !
    > !return ((string)(results[0]));
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    > !
    > !("CasClientConfig",
    > !
    > !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    > !
    > !lientConfig",
    > !
    > !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    > !
    > !ClientConfig")]
    > !
    > ![return:
    > !
    > !System.Xml.Serialization.SoapElementAttribute("getObjectConfigReturn")]
    > !
    > !public string getObjectConfig(string in0) {
    > !
    > !object[] results = this.Invoke("getObjectConfig", new object[] {
    > !
    > !in0});
    > !
    > !return ((string)(results[0]));
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > !public System.IAsyncResult BegingetObjectConfig(string in0,
    > !
    > !System.AsyncCallback callback, object asyncState) {
    > !
    > !return this.BeginInvoke("getObjectConfig", new object[] {
    > !
    > !in0}, callback, asyncState);
    > !
    > !}
    > !
    > !/// <remarks/>
    > !
    > !public string EndgetObjectConfig(System.IAsyncResult asyncResult) {
    > !
    > !object[] results = this.EndInvoke(asyncResult);
    > !
    > !return ((string)(results[0]));
    > !
    > !}
    > !
    > !}
    > !
    > !
    > !
    > !
    > !
    >
    Ramana, Sep 27, 2003
    #19
  20. Hello Romana,

    I am glad that the root cause is found. To find out more informatin on how
    this registry key is created, you could use a tool named RegMon in
    www.sysinternals.com to see when and which program modifies it.

    Hope that helps.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !From: "Ramana" <>
    !References: <05e601c34bee$8a519d50$>
    <>
    <>
    <#>
    <>
    <>
    <uBr$pg$>
    <>
    <n70ERa$>
    !Subject: Re: "The operation has timed-out." exception on WinXP
    !Date: Sat, 27 Sep 2003 12:58:43 +0530
    !Lines: 383
    !X-Priority: 3
    !X-MSMail-Priority: Normal
    !X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
    !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
    !Message-ID: <OtMZ$>
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !NNTP-Posting-Host: skater.hyd.deshaw.com 149.77.163.156
    !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl
    microsoft.public.dotnet.framework.aspnet.webservices:19588
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !
    !Hi Yanhong Huang,
    !
    !Thanks for the reply.
    !
    !I am able to consume other web services created by ASP.NET and the WSDL
    !generated for ASP webservice and jboss web service are identical.
    !I did some expernimentation with the problamatic profile and found
    yesterday
    !evening that a registry key is creating the problem
    !Here is the key
    !([HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
    !Settings\Connections]\DefaultConnectionSettings)
    !I think SOAP is using the default proxy settings available in the user
    !profile. The application is working after removing this key. We also found
    !another fix by setting the proxy preoperty of soap object to 'empty proxy'
    !and found the program working fine. We are going to apply this solution in
    !our project.
    !However, I could not find how (and Which programe changed the key) this
    !registry key is changed to a particular user.
    !
    !Any idea on this will help us to document the problem more clearly so taht
    !other teams will not face a similar problem.
    !
    !Thanks,
    !Ramana
    !
    !
    !"Yan-Hong Huang[MSFT]" <> wrote in message
    !news:n70ERa$...
    !> Hello Ramana,
    !>
    !> Thanks for posting in the group.
    !>
    !> Here is some suggestions for you:
    !>
    !> 1) If you create web reference in .NET IDE, will u meet it?
    !>
    !> 2) Please correct to other web services to see if the problem is there?
    !>
    !> 3) Use SoapTrace tool in soap toolkit to compare the difference of soap
    !> message.
    !>
    !> If you still can't find out the reason, I suggest you contact Microsoft
    !> Product Support Service in order that a support professional will work
    !with
    !> you specially on this problem. Here is the link for your reference:
    !>
    !http://support.microsoft.com/common/international.aspx?rdpath=fh;en-us;cnta
    c
    !> tms
    !>
    !> Best regards,
    !> Yanhong Huang
    !> Microsoft Online Partner Support
    !>
    !> Get Secure! - www.microsoft.com/security
    !> This posting is provided "AS IS" with no warranties, and confers no
    !rights.
    !>
    !> --------------------
    !> !From: "Ramana" <>
    !> !References: <05e601c34bee$8a519d50$>
    !> <>
    !> <>
    !> <#>
    !> <>
    !> <>
    !> <uBr$pg$>
    !> !Subject: Re: "The operation has timed-out." exception on WinXP
    !> !Date: Thu, 25 Sep 2003 16:33:20 +0530
    !> !Lines: 294
    !> !X-Priority: 3
    !> !X-MSMail-Priority: Normal
    !> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
    !> !X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
    !> !Message-ID: <>
    !> !Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
    !> !NNTP-Posting-Host: skater.hyd.deshaw.com 149.77.163.156
    !> !Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
    !> !Xref: cpmsftngxa06.phx.gbl
    !> microsoft.public.dotnet.framework.aspnet.webservices:19534
    !> !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
    !> !
    !> !Hi,
    !> !I am facing a similar ptoblem but wirh soap request.
    !> !
    !> !Here are the problem details. I am in deep trouble. Please help me
    fixing
    !> !the problem.
    !> !
    !> !
    !> !I am building a Windows Forms application to consume Webservices
    provided
    !> !
    !> !by the jboss server. I used the Windows WSDL.exe tool to generate the
    !proxy
    !> !
    !> !code. The proxy code file has been added to my windows forms aplication.
    !> !
    !> !When the exposed webservice methods are called, application gives the
    !timed
    !> !
    !> !out error("The operation has timed-out."). There is no proxy between the
    !> !
    !> !client and server.
    !> !
    !> !We checked that the server is sending response properly but the my
    !> !
    !> !webrequest is unable to recieve the response.
    !> !
    !> !This problem is happening after working for some time not every time.
    !> !
    !> !However, once this problem comes, I am not able to run the same
    !> !
    !> !application on any machine but other users are able to run the same
    !> !
    !> !application on the same machine. With this, we assumed that my roaming
    !> !
    !> !profile got corrupted and restored some old profile then I am able to
    run
    !> !
    !> !the application again. The same thing happend to many of my team members
    !> !
    !> !also.
    !> !
    !> !I think profile corruption is very dangerous and we need some urgent
    !> !
    !> !solution for this before rolling my application to actual users.
    !> !
    !> !Advace Thanks
    !> !
    !> !Ramana
    !> !
    !> !
    !> !
    !> !Here is the code snippet:
    !> !
    !> !//Web Service method called like below
    !> !
    !> !ClientConfigLocalService ccls = new ClientConfigLocalService();
    !> !
    !> !string xmlConfig = ccls.getURLs("4545454");
    !> !
    !> !
    !> !
    !> !//ClientConfigLocalService.CS (WSDL tool generated file)
    !> !
    !>
    !!//------------------------------------------------------------------------
    -
    !> !
    !> !-
    !> !
    !> !----
    !> !
    !> !// <autogenerated>
    !> !
    !> !// This code was generated by a tool.
    !> !
    !> !// Runtime Version: 1.0.3705.0
    !> !
    !> !//
    !> !
    !> !// Changes to this file may cause incorrect behavior and will be lost
    !> !
    !> !if
    !> !
    !> !// the code is regenerated.
    !> !
    !> !// </autogenerated>
    !> !
    !>
    !!//------------------------------------------------------------------------
    -
    !> !
    !> !-
    !> !
    !> !----
    !> !
    !> !//
    !> !
    !> !// This source code was auto-generated by wsdl, Version=1.0.3705.0.
    !> !
    !> !//
    !> !
    !> !using System.Diagnostics;
    !> !
    !> !using System.Xml.Serialization;
    !> !
    !> !using System;
    !> !
    !> !using System.Web.Services.Protocols;
    !> !
    !> !using System.ComponentModel;
    !> !
    !> !using System.Web.Services;
    !> !
    !> !
    !> !
    !> !/// <remarks/>
    !> !
    !> ![System.Diagnostics.DebuggerStepThroughAttribute()]
    !> !
    !> ![System.ComponentModel.DesignerCategoryAttribute("code")]
    !> !
    !> ![System.Web.Services.WebServiceBindingAttribute
    !> !
    !> !(Name="CasClientConfigSoapBin
    !> !
    !> !ding",
    !> !
    !> !Namespace="http://mycompany.com:8080/jboss-net/services/CasClientCo
    !> !
    !> !nfig")]
    !> !
    !> !public class ClientConfigLocalService :
    !> !
    !> !System.Web.Services.Protocols.SoapHttpClientProtocol {
    !> !
    !> !/// <remarks/>
    !> !
    !> !public ClientConfigLocalService() {
    !> !
    !> !this.Url =
    !> !
    !> !"http://mycompany.com:8080/jboss-net/services/CasClientConfig";
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    !> !
    !> !("CasClientConfig",
    !> !
    !> !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    !> !
    !> !lientConfig",
    !> !
    !> !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    !> !
    !> !ClientConfig")]
    !> !
    !> ![return: System.Xml.Serialization.SoapElementAttribute
    !> !
    !> !("getURLsReturn")]
    !> !
    !> !public string getURLs(string in0) {
    !> !
    !> !object[] results = this.Invoke("getURLs", new object[] {
    !> !
    !> !in0});
    !> !
    !> !return ((string)(results[0]));
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> !public System.IAsyncResult BegingetURLs(string in0,
    !> !
    !> !System.AsyncCallback
    !> !
    !> !callback, object asyncState) {
    !> !
    !> !return this.BeginInvoke("getURLs", new object[] {
    !> !
    !> !in0}, callback, asyncState);
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> !public string EndgetURLs(System.IAsyncResult asyncResult) {
    !> !
    !> !object[] results = this.EndInvoke(asyncResult);
    !> !
    !> !return ((string)(results[0]));
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    !> !
    !> !("CasClientConfig",
    !> !
    !> !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    !> !
    !> !lientConfig",
    !> !
    !> !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    !> !
    !> !ClientConfig")]
    !> !
    !> ![return:
    !> !
    !> !System.Xml.Serialization.SoapElementAttribute("getServerVersionReturn")]
    !> !
    !> !public string getServerVersion() {
    !> !
    !> !object[] results = this.Invoke("getServerVersion", new object[0]);
    !> !
    !> !return ((string)(results[0]));
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> !public System.IAsyncResult BegingetServerVersion(System.AsyncCallback
    !> !
    !> !callback, object asyncState) {
    !> !
    !> !return this.BeginInvoke("getServerVersion", new object[0],
    !> !
    !> !callback,
    !> !
    !> !asyncState);
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> !public string EndgetServerVersion(System.IAsyncResult asyncResult) {
    !> !
    !> !object[] results = this.EndInvoke(asyncResult);
    !> !
    !> !return ((string)(results[0]));
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> ![System.Web.Services.Protocols.SoapRpcMethodAttribute
    !> !
    !> !("CasClientConfig",
    !> !
    !> !RequestNamespace="http://mycompany.com:8080/jboss-net/services/CasC
    !> !
    !> !lientConfig",
    !> !
    !> !ResponseNamespace="http://mycompany.com:8080/jboss-net/services/Cas
    !> !
    !> !ClientConfig")]
    !> !
    !> ![return:
    !> !
    !> !System.Xml.Serialization.SoapElementAttribute("getObjectConfigReturn")]
    !> !
    !> !public string getObjectConfig(string in0) {
    !> !
    !> !object[] results = this.Invoke("getObjectConfig", new object[] {
    !> !
    !> !in0});
    !> !
    !> !return ((string)(results[0]));
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> !public System.IAsyncResult BegingetObjectConfig(string in0,
    !> !
    !> !System.AsyncCallback callback, object asyncState) {
    !> !
    !> !return this.BeginInvoke("getObjectConfig", new object[] {
    !> !
    !> !in0}, callback, asyncState);
    !> !
    !> !}
    !> !
    !> !/// <remarks/>
    !> !
    !> !public string EndgetObjectConfig(System.IAsyncResult asyncResult) {
    !> !
    !> !object[] results = this.EndInvoke(asyncResult);
    !> !
    !> !return ((string)(results[0]));
    !> !
    !> !}
    !> !
    !> !}
    !> !
    !> !
    !> !
    !> !
    !> !
    !>
    !
    !
    !
    Yan-Hong Huang[MSFT], Sep 29, 2003
    #20
    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. Matt
    Replies:
    0
    Views:
    3,959
  2. =?Utf-8?B?S2h1cnJhbSBJc2hmYXEgUmF0aG9y?=

    Operation has timed out in ASP.Net Application

    =?Utf-8?B?S2h1cnJhbSBJc2hmYXEgUmF0aG9y?=, Sep 2, 2004, in forum: ASP .Net
    Replies:
    0
    Views:
    4,214
    =?Utf-8?B?S2h1cnJhbSBJc2hmYXEgUmF0aG9y?=
    Sep 2, 2004
  3. =?Utf-8?B?U2FjaGluIFN1cmFuYQ==?=

    System.WebException | The operation has timed out

    =?Utf-8?B?U2FjaGluIFN1cmFuYQ==?=, Feb 2, 2005, in forum: ASP .Net
    Replies:
    5
    Views:
    10,091
    William F. Robertson, Jr.
    Feb 8, 2005
  4. news.microsoft.com

    Exception: The operation has timed-out.

    news.microsoft.com, Oct 28, 2005, in forum: ASP .Net
    Replies:
    1
    Views:
    2,797
    Kevin Spencer
    Oct 28, 2005
  5. Alex Litvak

    random "The operation has timed-out." exception in vb.net

    Alex Litvak, Oct 8, 2004, in forum: ASP .Net Web Services
    Replies:
    1
    Views:
    286
    Sachin Surana
    Feb 2, 2005
Loading...

Share This Page