Just a word of caution, related to best practices
1. Adjusting the machine config file in develoment is a risky bet. The
machine config is typically managed by IT policy in production
environments, and it is always a poor bet to assume that IT will go along
with changes to the machine.config file during application install.
2. Find a way to make your validation faster. If it is taking longer than
90 seconds, you have other issues such as user-retry, user hates
application, user assumes it doesn't work, and load management issues in
high volume situations. You should try to make your designs accept and
respond (or complete) any web service call in subsecond measurements so
that you don't introduce the risk of exhausting the IIS thread pool. This
is again an area where production personnell will be very concerned if they
want to deploy your application on a shared server and your application is
poorly behaved.
My .02cents
Dan Rogers
--------------------
From: "Derek Harmon" <lo*******@msn.com>
References: <D8**********************************@microsoft.co m>
Subject: Re: Client Timeout - HELP
Date: Sat, 13 Nov 2004 23:57:26 -0500
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <eE**************@tk2msftngp13.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: mailgw.infragistics.com 216.113.236.146
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!tk2msftngp13
.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7415
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
"Dan" <Da*@discussions.microsoft.com> wrote in message
news:D8**********************************@microsof t.com...
that the data comes from is mamouth. So, it may take a long time for the
validation query to complete.
Unforuntatley, I tend to get a timeout message on my client which is not
good. I want the client to wait until it gets a response. Can I adjust the
amount of time that it waits? If so where is that at?
In a synchronous web service call, you can set a timeout period (in
milliseconds)
using the Timeout property of your web service proxy, before you make any
web method calls on it.
However, if what you're receiving is a fault relating to HTTP response codes
404, 408, 500, 503 or 504 then it is a server time out. You can tell the
client
to wait for Timeout.Infinite, but most servers will drop you after awhile,
and
there's nothing you can do about that from the client.
If you have control over the server, and it's ASP.NET, then you can increase
the executionTimeout attribute value (defaults to 90 secs) on the
<httpRuntime>
element in the "machine.config" file.
Derek Harmon
