Remoting idletimeout not working

[koganty]

We are running JBoss 4.0.5 with EJB3 RC9 on JDK1.6 with Remoting 1.4.6.

Our standalone client uses the socket transport to connect to the server and invoke methods on the EJB3 SLSB.

What I see is that the SocketInvoker threads are created to handle the client requests, but these threads just linger around and never go away even long after their idleTimeout.

Below is the connector configuration:

<mbean code="org.jboss.remoting.transport.Connector"
 name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"
 display-name="Socket transport Connector">
 <depends>jboss.aop:service=AspectDeployer</depends>
 <attribute name="Configuration">
 <config>
 <invoker transport="socket">
 <attribute name="serverBindPort">${jboss.ejb3.remoting.port}</attribute>
 <attribute name="maxPoolSize">100</attribute>
 <attribute name="backlog">50</attribute>
 </invoker>
 <handlers>
 <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
 </handlers>
 </config>
 </attribute>
 </mbean>

And here is the thread dump for SocketInvoker:


Thread: SocketServerInvokerThread-10.255.48.46-6 : priority:5, demon:false, threadId:5910, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)Thread: SocketServerInvokerThread-10.255.48.46-7 : priority:5, demon:false, threadId:5912, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)Thread: SocketServerInvokerThread-10.255.48.46-8 : priority:5, demon:false, threadId:5915, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)Thread: SocketServerInvokerThread-10.255.48.46-9 : priority:5, demon:false, threadId:5927, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)Thread: SocketServerInvokerThread-10.255.48.46-10 : priority:5, demon:false, threadId:5928, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)Thread: SocketServerInvokerThread-10.255.48.46-11 : priority:5, demon:false, threadId:5937, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)Thread: SocketServerInvokerThread-10.255.48.46-12 : priority:5, demon:false, threadId:5945, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)Thread: SocketServerInvokerThread-10.255.48.46-13 : priority:5, demon:false, threadId:5946, threadState:WAITING, threadLockName:[e-mail](Native Method)java.lang.Object.wait(Object.java:485)org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:282)

[tom.elrod]

http://labs.jboss.com/portal/jbossremoting/docs/guide/ch05.html#d0e1120 explains how the threading works in detail, but in short, the connection is maintained between client and server even after the requests are made.

A idle timeout has been added (see http://jira.jboss.com/jira/browse/JBREM-607) which will clean up idle threads before the connection timout occurs, but will not be part of a remoting 1.4.x release (added to 2.2.0).