Publishing schema as web service... client side timeout problem

Tech-Archive recommends: Speed Up your PC by fixing your registry

I publish schema as web service. Client side gets timeout error. I counted
the time, it's exactly 110 seconds.

I've already changed the client code to use a very long timeout, 600000
milliseconds, but it still timeout at 110 seconds. So there has to be
something on server side to control the timeout.

Is there any settings in web.config or machine.config that I can play with?
I am using 2003 server and 2.0 framework.

Following is what I got from MSDN website and it proves that the timeout
happens on server side. But how can I change this
HttpServerUtility.ScriptTimeout property?

------------------------------------------------------------------------------------------------

Web services generated with the Web Services Publishing Wizard in BizTalk
Server 2006 are configured by default with a script timeout value of 110
seconds. This is the default value for the .NET Framework 2.0
HttpServerUtility.ScriptTimeout property. Web clients that use .NET
Framework 2.0 are configured by default with a request timeout value of 100
seconds. This is the default value for the .NET Framework 2.0
HttpWebRequest.Timeout property.

If Web clients that use .NET framework 2.0 are calling a Web Service
generated with the BizTalk Server 2006 Web Services Publishing Wizard, it is
possible that the client cannot receive server script timeout errors because
the client request timeout occurs first by default. To resolve this problem
you can do one of the following:

a.. Increase the client request timeout to a value greater than the server
script timeout by increasing the value for the HttpWebRequest.Timeout
property on the client.

b.. Reduce the server script timeout to a value less than the client
request timeout by reducing the value for the
HttpServerUtility.ScriptTimeout property on the server.



.

Relevant Pages

  • Re: Webservice problem (after iisreset)
    ... I was speaking about whatever means you're suing the make the call from the client. ... If it already waits one minute for the failure then it sounds like the timeout is already high enough. ... So use wsdl.exe to generate a .NET proxy to your webservice to see if that style of client has the same problems or not. ... If it does, then it sounds like something on the server, if it does not then it's likley your HTC framework. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Timeout value in new RDP 6.0 client
    ... I would suspect the problem is not so much the timeout as the severely overloaded server. ... Most likely you completed the first few stages of the connection, leading the client to believe everything was okay, but the server wasn't establishing the connection in the time you expected due to the load. ...
    (microsoft.public.windows.terminal_services)
  • Re: web serivce: client side timeout?
    ... client side but only from the server side. ... System.Net.Sockets.SocketException: A connection attempt failed ... asyncResult, Int32 timeout, Exception& exception) ... John Saunders | MVP - Windows Server System - Connected System ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: detecting the (brute) disconnection of a client
    ... crashed, and if an exception occurs, then the client is deconnected. ... You can either use the timeout itself as an indication of connection failure, or you can attempt to send data after the timeout. ... The server has no way to know if the connection has failed due to a client-side crash, or simply due to a temporary problem with the network. ... IMHO, it would be better to simply let the server continue to assume that the connection is valid unless there is some explicit, non-arbitrary verification that it's not. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: web serivce: client side timeout?
    ... I have a windows forms application that makes calls to a web service. ... client side but only from the server side. ... System.Net.Sockets.SocketException: A connection attempt failed ... asyncResult, Int32 timeout, Exception& exception) ...
    (microsoft.public.dotnet.framework.webservices)