1
Vote

Timeout Exception Not Intercepted

description

A colleague of mine using this encountered a scenario where a timeout exception is thrown, but it is not a communication exception so the proxy doesn't recover as with other communication exceptions. This means that, like with a regular proxy, the proxy is not usable after the exception.
 
I will try to duplicate this to catch the exception. But, more importantly, this means there must be a way to "recover" when there is an "unrecoverable" error. For example I might throw an event indicating the proxy is now "out-of-service" so that the client code can respond and recreate. This should be extremely rare.

comments