Hi all,I'm working with WebServices and I have a working service, but I've noticed that if the web service server is non-responsive, the WOWebServiceClient constructor hangs the entire WO client app. Moving the constructor to a separate thread did not solve the problem.
After much debugging, I tracked the problem down to a socketRead0() native method (trace is in the attached image). Setting
-Djava.net.connectiontimeout=2(2 seconds. Default is -1 for infinity) seemed to cure the problem. The constructor then throws a java.lang.IllegalArgumentException caused by a java.net.ConnectException (connection refused). However, if I set the timeout to 30 seconds, the original problem returns... sporadically. Sometimes, it throws the exception as expected, sometimes it does not.
So I'm left with an app that feels like a ticking time bomb. One bad constructor call can hang the entire instance. I'm wondering if anyone else has seen this and knows a fix or a workaround.
Thanks everyone, Ramsey
<<inline: Picture 8.png>>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
