NET Web Service (asmx) Timeout Problem?

Firstly: See Steven ChengMSFT response here about timeouts. There is a execution timeout you can set for httpRuntime. He says something interesting after that, which is "Also, make sure that you've set the 'compilation debug="false"' as to make the timeout work correctly Besides the fact that something may be terribly wrong on their end (or the data returned is so voluminous/ I'm not going to judge - might be a good reason), have you tried calling their operation Asynchronously?

Same results? I guess it would take an hour YourVendor. WebService ws = new YourVendor.WebService(); ws.

LongRunningOperationCompleted += new YourVendor. LongRunningOperationEventHandler(ws_LongRunningOperationCompleted); ws. LongRunningOperationAsync(); // Implement the ws_LongRunningOperationCompleted handler (stub will auto generate) The completed event handler will have a specific event args param, which will contain the results, for event args e, e.

Result should have what you need when it completes.

Firstly: See Steven ChengMSFT response here about timeouts. There is a execution timeout you can set for httpRuntime. He says something interesting after that, which is "Also, make sure that you've set the 'compilation debug="false"' as to make the timeout work correctly" Besides the fact that something may be terribly wrong on their end (or the data returned is so voluminous/ I'm not going to judge - might be a good reason), have you tried calling their operation Asynchronously?

Same results? I guess it would take an hour YourVendor. WebService ws = new YourVendor.WebService(); ws.

LongRunningOperationCompleted += new YourVendor. LongRunningOperationEventHandler(ws_LongRunningOperationCompleted); ws. LongRunningOperationAsync(); // Implement the ws_LongRunningOperationCompleted handler (stub will auto generate) The completed event handler will have a specific event args param, which will contain the results, for event args e, e.

Result should have what you need when it completes.

The web. Config file on the client's side had no httpRuntime element, so I added one with a very large timeout, then started it up again. We'll see in an hour, thanks!

– Barry Fandango Jun 17 '10 at 19:57 As for the async option, I could open the hood and change the call to async. Are those generally more tolerant to timeouts, do they execute differently? The data is not too voluminous, but it has to be processed on the other end before the results are returned, and whoever wrote the processing code did not have an eye to performance past a certain data size.

– Barry Fandango Jun 17 '10 at 19:59.

This is some good guidance: msdn.microsoft.com/en-us/library/ff64778....

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.