Re: axis call now gives java.net.SocketTimeoutException
Re: axis call now gives java.net.SocketTimeoutException
- Subject: Re: axis call now gives java.net.SocketTimeoutException
- From: Chuck Hill <email@hidden>
- Date: Wed, 5 Apr 2006 20:34:47 -0700
On Apr 5, 2006, at 8:13 PM, Baiss Eric Magnusson wrote:
I make the following call, which used to work,
String endpoint = "http://services.xmethods.com:80/soap";;
org.apache.axis.client.Call call = (org.apache.axis.client.Call)
service.createCall();
call.setOperationName( new javax.xml.namespace.QName
( "urn:xmethods-delayed-quotes", "getQuote" ));
...
Float ret = (Float) call.invoke( new Object[] { stockSymbol } );
and the <call.invoke> throws a <java.net.SocketTimeoutException>.
I upped the JavaMonitor <Lifebeat Interval> to <300> and still get
the error, I used to be able to run most of the time with an
interval of <60>.
I'd doubt that this exception is in any way related to the Lifebeat
interval.
You might take a look at something like:
#
# These properties specify the default connect and read timeout
(resp.) for
# the protocol handler used by java.net.URLConnection.
#
# sun.net.client.defaultConnectTimeout specifies the timeout (in
milliseconds) to
# establish the connection to the host. For example for http
connections it is the
# timeout when establishing the connection to the http server. For
ftp connection
# it is the timeout when establishing the connection to ftp servers.
#
# sun.net.client.defaultReadTimeout specifies the timeout (in
milliseconds) when
# reading from input stream when a connection is established to a
resource.
#
# Reference http://java.sun.com/j2se/1.4.2/docs/guide/net/
properties.html
#
# The defaults are -1 (a.k.a. forever). Set these to a more
reasonable setting to
# prevent the app from blocking on information pulled from slow
external sources
#
sun.net.client.defaultConnectTimeout=5000
sun.net.client.defaultReadTimeout=5000
But you might want to look for an network problem. Perhaps someone
has added some restrictions to the firewall?
Chuck
I'm not able to test on the development machine as the
<call.invoke> throws a
(502) Proxy Error
so there must be some setup done on the MacOSX server that is not
done on a simple MacOSX box.
----
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:
40global-village.net
This email sent to email@hidden
--
Coming in 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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden