views:

697

answers:

1

Hi All, We have a client application that has reference to a webservice. We had set the timeout property on the webclientprotocol object to 50 (ms) and wanted to observe what goes on. We tied up a long running webmethod that returns a huge DataSet to the client. When the default value was there, the DataSet was returned properly to the client. When we changed this to 50(ms), we did not observe anything. Our assumption was that there would be some kind of exception that occurs on the client side since the timeout has occurred. Can anyone please explain what is going on here

Thanks Raj

+1  A: 

The documentation is unfortunately unclear. When you say you "didn't observe anything" what exactly do you mean? Did the code hang forever? Was an exception thrown? Presumaby a valid DataSet wasn't returned.

I would expect a TimeoutException to be thrown but I'm surprised that wasn't entirely obvious in your client code. You're not swallowing exceptions, are you?

Are you executing the call synchronously or asynchronously? If it's asynchronous, I'd expect the callback to be executed and then the exception to be thrown on the "EndXxx" call.

I strongly recommend that you write a short console application which just calls the web service, just to see what happens.

Jon Skeet