Register / Login
this forum made possible by our volunteer staff, including ...
Stephan van Hulst
Client-side timeout effecting try... finally call
posted 3 years ago
I have a web service which contains a try.. finally call to ensure a pooled resource is freed.
The web service content can sometimes execute a bit slowly... over 30 seconds.
What I am finding is that if the client is set to timeout, and does before the call is complete the finally block is not called and the resource does not get freed.
Is this expected behaviour? I really did not expect this to happen.
-- later --
my mistake... it does get to the finally block... eventually.
Boost this thread!
Timeout Exception while connecting to a web service
Container Time Out
Connection failure - web service
FileNotFoundException - Too many files open
Setting Timeout with WebSphere generated services