Running into exception while using EJB3 Beta1 and 4.0.3RC1

[koganty]

Basically we are polling the server from a client every 1 sec using a StatelessSessionBean and we run into this exception once in a while :

2005-07-28 18:06:31,421 DEBUG [ClientPoller][ClientPoller]: Initiating a poll......
2005-07-28 18:07:31,984 DEBUG [ClientPoller][ClientPoller]:
java.lang.reflect.UndeclaredThrowableException
at $Proxy2.getResponses(Unknown Source)
at com.extremenetworks.epicenter.client.common.ClientSession.getResponses(ClientSession.java:108)
at com.extremenetworks.epicenter.client.common.ClientPoller.pollResponses(ClientPoller.java:103)
at com.extremenetworks.epicenter.client.common.ClientPoller.poll(ClientPoller.java:96)
at com.extremenetworks.epicenter.client.common.ClientPoller.run(ClientPoller.java:76)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.rmi.ConnectException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketTimeoutException: Read timed out
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:266)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:117)
at org.jboss.remoting.Client.invoke(Client.java:201)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:40)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
at org.jboss.aspects.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:34)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:79)
... 6 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2490)
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2500)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1267)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:72)
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:244)
... 17 more

Thanks,
Raju

[tom.elrod]

Do you have a sample app that will reproduce this?

[triathlon98]

I have posted a message about this problem in the EJB3 forums, see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890923#3890923

The problem is that the remoting framework uses a default timeout of 60s, while the ejb layer has a default tx timeout of 300s. As a result of this combination, when the action takes longer than 60s, the client receives a TimeoutException while the work itself is still continuing at the server side.

As mentioned in the above post, I already tried changing the configuration, but that failed.

In principle, for the ejb stuff, I think the connection timeout should always be longer than the transaction timeout to avoid strange problems.

Joachim

[tom.elrod]

Ok. Let's keep this thread down to one forum. I'll reply on the ejb3 forum.