WSE 3 + Long Running Request = Timeout

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have a request that could take up to 5-10 minutes to process on the server side. There's no way around it, and believe me if there was a way to avoid this, I would be very happy indeed, but there isn't. (and normally this will take a couple of seconds but if the person hasn't used the web service in quite a while it could take a very long while (data base size related)).

Anyhow, when I run the request it runs for about 5 mintues and then times out on the client side. It appears to still be running on the server side, at least the wp3 process is still going nuts like it's doing it's work.

On start of the Service when I create it I set the Timeout = Int32.MaxValue.

I've tried -1 and it doesn't matter. 0 just errors.

I've set on the server side the HTTP requestTimeout = 3600 (1 hour) and it doesn't matter.

How do I get the client to wait longer before timing out? (I get the "server focibly closed the connection..." as the internal error and it's on the reponse that it's erroring which leads me to believe that it's something in my config on the server not the client, but...)

Thanks!

James Han***

.

Quantcast