JBoss EAP 5 / 4 is limiting EJB RMI Client connections to 50 leads to IllegalStateException: Timeout waiting for a free socket
Issue
- We are calling jboss EAP J2EE services from a remote client, (tomcat web server), by doing a JNDI lookup and invoking the EJB. It seems to be limmited to 50 J2EE connections per client and when we have 50 waiting, further client requests hang somewhere. Multiple clients all get 50 connections, so 1 app server can handle more than 50. Are there JBoss configuration files controlling this limit for the client running from tomcat?
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://my.jboss.server:3873/?invokerDestructionDelay=5000&timeout=300000]
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:831)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169)
at org.jboss.remoting.Client.invoke(Client.java:2070)
at org.jboss.remoting.Client.invoke(Client.java:879)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
...
Caused by: java.lang.IllegalStateException: Timeout waiting for a free socket
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:1129)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:816)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169)
at org.jboss.remoting.Client.invoke(Client.java:2070)
at org.jboss.remoting.Client.invoke(Client.java:879)
...
Environment
- JBoss Enterprise Application Platform (EAP)
- 5.x
- 4.x
- JBoss Remoting 2.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
