cdeclog

삼양목장..

인사동..

이유진님..

경복궁..

나디아님..

하늘도 보고..

불장난도 하고..

풀도 보고..

땀도 좀 식히고..

Solving "The underlying connection was closed: An unexpected error occurred on a send." (Webservices)

Sometimes when you invoke a webservice the call fails with the following exception:

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at ...

In some cases the first call to the webservice works just fine, but if in the following few minutes no new call to the webservice is made, the next call would throw the exception shown above. This problem could be solved by altering the generated proxy class; in the GetWebRequest function the KeepAlive property must be set to false. This can be accomplished by following these steps:

• Add a Web Reference using the normal way (if you haven't already added one ofcourse).
• Make sure Show All Files menu item is enable in the Project menu.
• In the Solution Explorer window, navigate to:
  • Web References
    • <Name of your webservice>
      • Reference.map
        • Reference.cs (or .vb)
• Open the Reference.cs file and add following code in the webservice proxy class:
  protected override System.Net.WebRequest GetWebRequest(Uri uri)
  {
   System.Net.HttpWebRequest webRequest =
    (System.Net.HttpWebRequest) base.GetWebRequest(uri);
   webRequest.KeepAlive = false;
   return webRequest;
  }

10월 1일이 되면 공식적으로 청계천이 복원된다.

날씨가 좋은 탓일까..

사람들이 북적된다.

여기는..