On Apr 14, 2006, at 11:24 AM, Baiss Eric Magnusson wrote:
I am having more problems with the Axis stockquote code. The
previous timeout settings worked for a while.
What did you set them to?
I get <no instance available> back at the browser page due to a
timeout caused by the line of code
Float ret = (Float) call.invoke( new Object[] { symbol } );
not responding.
That sounds like the woadaptor Receive timeout is less than the
java.net.whatever timeout you set before. The Java one should be less.
If you refresh the page I will trap the exception
<java.net.SocketTimeoutException>
and calmly inform the user that the stock quote service is
currently unavailable.
How can I trap the first problem <no instance available> in the
java code without the user having to force a refresh?
You can't. The first problem is reported by the woadaptor (e.g. the
CGI or mod_webobjects). You can't have any control over that from
your application. The thing to do is to adjust the timeouts relative
to each other so that the socket timeout happens before the receive
timeout.
Chuck
--
Coming in late 2006 - an introduction to web applications using
WebObjects and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
