Re (progress): no instance available due to timeout
Re (progress): no instance available due to timeout
- Subject: Re (progress): no instance available due to timeout
- From: Baiss Eric Magnusson <email@hidden>
- Date: Mon, 17 Apr 2006 11:04:47 -0700
Chuck,
Thanks much for below, things are better.
The timeouts I have worked with are:
sun.net.client.defaultReadTimeout=15000
in the Properties file loaded in Web Server, this time in milli-
seconds
Receive timeout: 180
in the Adaptor Settings of JavaMonitor, this time in seconds
and
Lifebeat Interval: 120 of the Instance Settings of JavaMonitor, the
Lifebeat interval doesn't seem to have an affect in the overall
situation.
By setting the <Receive timout> to 120, from its default, I was able
to trap the <java.net.SocketTimeoutException>.
However the Axis call is always failing on the first stock read
attempted
and
the exception always occurs 60 seconds after I make the call.
So, I don't know where the 60 seconds is coming from?
And, is it possible the Axis stuff
"http://services.xmethods.com:80/soap";;
is just unavailable a lot of the time?
On Apr 14, 2006, at 7:45 PM, Chuck Hill wrote:
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
----
Baiss Eric Magnusson
<http://www.Track-Your-Finances.com>
<http://www.CascadeWebDesign.com>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden