how to set timeout?

[peterlan]

Hi, this is a follow-up to my previous post. I've got a long-running function
exposed as a web service. It can take up to 3 or 4 minutes to complete
(rendering a 300 page pdf from xsl-fo). I have the asp script timeout for the
web app the service runs as set to 600 seconds. I have the timeout for the
webservice on the consuming end set to the same. I still get a timeout error,
however. The response that comes from the webservice is an asp error page
saying "Request Timed Out". I do NOT get this error when the project is
compiled with debugging. Is there some timeout setting that I'm missing? Can
anyone offer any pointers?

Thanks

[Manohar Kamath]

There are two places you may have to change:

1. Change the ASP.NET timeout, not ASP one:

http://www.devx.com/vb2themax/Tip/18803

This is the most likely culprit of your errors

2. Use the Timeout property of your proxy class to set the proper time on
the client.

WebReference.ProxyClass myProxy = new WebReference.ProxyClass();
// Set the timeout in milliseconds -- e.g. 100 seconds
myProxy.Timeout = 100000;

Hope that helps.
--
Manohar Kamath
Editor, .netWire
www.dotnetwire.com
"peterlan" <pe******@discussions.microsoft.com> wrote in message
news:C2**********************************@microsof t.com...

Hi, this is a follow-up to my previous post. I've got a long-running function exposed as a web service. It can take up to 3 or 4 minutes to complete
(rendering a 300 page pdf from xsl-fo). I have the asp script timeout for the web app the service runs as set to 600 seconds. I have the timeout for the
webservice on the consuming end set to the same. I still get a timeout error, however. The response that comes from the webservice is an asp error page
saying "Request Timed Out". I do NOT get this error when the project is
compiled with debugging. Is there some timeout setting that I'm missing? Can anyone offer any pointers?

Thanks

[peterlan]

That was it. Thanks!

"Manohar Kamath" wrote:

There are two places you may have to change:

1. Change the ASP.NET timeout, not ASP one:

http://www.devx.com/vb2themax/Tip/18803

This is the most likely culprit of your errors

2. Use the Timeout property of your proxy class to set the proper time on
the client.

WebReference.ProxyClass myProxy = new WebReference.ProxyClass();
// Set the timeout in milliseconds -- e.g. 100 seconds
myProxy.Timeout = 100000;

Hope that helps.
--
Manohar Kamath
Editor, .netWire
www.dotnetwire.com
"peterlan" <pe******@discussions.microsoft.com> wrote in message
news:C2**********************************@microsof t.com...

Hi, this is a follow-up to my previous post. I've got a long-running

function

exposed as a web service. It can take up to 3 or 4 minutes to complete
(rendering a 300 page pdf from xsl-fo). I have the asp script timeout for

the

web app the service runs as set to 600 seconds. I have the timeout for the
webservice on the consuming end set to the same. I still get a timeout

error,

however. The response that comes from the webservice is an asp error page
saying "Request Timed Out". I do NOT get this error when the project is
compiled with debugging. Is there some timeout setting that I'm missing?

Can

anyone offer any pointers?

Thanks