SocketTimeout in client

[maheshp]

Hello All

i am connecting to server using java client, after setting socket time out attribute in "invokers-service.xml" to 300000 milli sec. i am getting the Socket timeout error after 60 seconds of waiting time(default time out value).
Server Version : Jboss-4.0.3sp1

For information i have pasted complete stack strace below.
if any configuration is missed out in server/ client, please let me know.

java.rmi.ConnectException: Failed to communicate. Problem during marshalling/un
marshalling; nested exception is:
java.net.SocketTimeoutException: Read timed out
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(Soc
ketClientInvoker.java:264)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.jav
a:112)
at org.jboss.remoting.Client.invoke(Client.java:226)
at org.jboss.remoting.Client.invoke(Client.java:189)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemot
eInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:98)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPr
opagationInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:98)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityC
lientInterceptor.java:40)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:98)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.
java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:98)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteP
roxy.java:88)
at $Proxy5.getTreeObject(Unknown Source)

Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Sourc
e)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read
(SerializableUnMarshaller.java:73)
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(Soc
ketClientInvoker.java:242)
... 27 more


Thanks in advance

Thanks and Regards
Mahesh

[tom.elrod]

Will need to make sure the timeout is getting set for the client. If are using remoting discovery to get the locator url for the client to use, then need to make sure the isParam attribute is set to true in your invokers-service.xml. For example:

<attribute name="timeout" isParam="true">60000</attribute>

This way, when the client gets the locator url with the timeout built in as a url parameter (i.e. socket://myhost:3453/?timeout=60000).

If you are creating the remoting Client class yourself and passing the locator url, will need to make sure you pass the timeout value. More info on this at http://labs.jboss.com/portal/jbossremoting/docs/guide/ch05.html#d0e668.

BTW, if using older version of remoting, the attribute is 'socketTimeout' and for 2.x is 'timeout'.

[maheshp]

Hello Mr. Tom,

i am using following code to get the remote objects,
Hashtable<Object,String> props = new Hashtable<Object,String> ();
props.put(
InitialContext.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
props.put(InitialContext.PROVIDER_URL, "jnp://127.0.0.1:1099");
props.put("java.naming.factory.url.pkgs", "org.jboss.naming");

InitialContext ctx = new InitialContext(props);
objSecurity = (Security) ctx.lookup(SecurityRemote.class.getName());

after setting the timeout attribute in invoker-service.xml to 120,000 it is taking the 60000 milli sec as default and it throwing timeout exception after 60000 ms.

please let me know any other options to get the remote objects, so i can avoid the timeout exception.

[tom.elrod]

Guess the real question is what is SecurityRemote? If it is an object that you created which creates a remoting Client instance, then need to make sure the locator url used when creating that remoting Client contains the client timeout.