Remoting Exception: Too many channels open

[prasad.deshpande]

Hi Guys,

I'm doing a load testing on my application with 7.1.0.Final & I'm getting following exception

{className="API" methodName="logout" componentSequenceNumber=900017 severity=13 errorType=4 errorMessage="An application server error occurred while logging out." nestedException.message="Failed to create remoting connection" nestedExceptio

n.stackTrace="javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: org.jboss.remoting3.ProtocolException: Too many channels open]

        at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)

        at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:117)

        at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)

        at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)

        at javax.naming.InitialContext.init(Unknown Source)

        at javax.naming.InitialContext.<init>(Unknown Source)

        at com.banctec.caseware.client.api.RemoteClientAPI.createCPC(RemoteClientAPI.java:132)

        at com.banctec.caseware.client.api.API.logout(API.java:662)

        at com.EJBTest.teardownTest(EJBTest.java:50)

        at org.apache.jmeter.protocol.java.sampler.JavaSampler.releaseJavaClient(JavaSampler.java:113)

        at org.apache.jmeter.protocol.java.sampler.JavaSampler.testEnded(JavaSampler.java:249)

        at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfEnd(StandardJMeterEngine.java:236)

        at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:454)

        at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.RuntimeException: org.jboss.remoting3.ProtocolException: Too many channels open

        at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:87)

        at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:108)

        ... 12 more

Caused by: org.jboss.remoting3.ProtocolException: Too many channels open

        at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:177)

        at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:307)

        at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:75)

        at org.jboss.naming.remote.client.cache.ConnectionCache$ConnectionWrapper.openChannel(ConnectionCache.java:95)

        at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:107)

        ... 12 more

"}

        at com.banctec.caseware.client.api.API.logout(API.java:674)

        at com.EJBTest.teardownTest(EJBTest.java:50)

        at org.apache.jmeter.protocol.java.sampler.JavaSampler.releaseJavaClient(JavaSampler.java:113)

        at org.apache.jmeter.protocol.java.sampler.JavaSampler.testEnded(JavaSampler.java:249)

        at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfEnd(StandardJMeterEngine.java:236)

        at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:454)

        at java.lang.Thread.run(Unknown Source)

I'm sure, there must be some setting/configuration to avoid this error. I'm running with 100 threads & looping 10 times per thread.

[jaikiran]

You have the new InitialContext() part in loop too? That's a bad practice. Each of that is going to create a separate connection and end up with issues like this. Also remember to do initialContext.close() wherever appropriate.

[prasad.deshpande]

You have the new InitialContext() part in loop too?

Not really, that's been done as a part of testSetup which is guaranteed to be called once per thread. However, I can try adding close() call at the end to see if that makes any difference..

[jaikiran]

Prasad Deshpande wrote:

You have the new InitialContext() part in loop too?

Not really, that's been done as a part of testSetup which is guaranteed to be called once per thread. However, I can try adding close() call at the end to see if that makes any difference..

Ah ok, so each thread is creating the InitialContext and I guess you have more than 40 such threads running simultaneously. Looking at the remoting code, although there's a property which allows this to be configured, it isn't used in any part of the code. So I don't see a way to configure this currently.

[prasad.deshpande]

so each thread is creating the InitialContext and I guess you have more than 40 such threads running simultaneously.

So in theory, let's assume 1 InitialContext per thread.. but it couldn't even reach 40.. It started giving me that exception just after reaching 24 instances..

[prasad.deshpande]

then how do I simulate load over say 100/200 concurrent users if this is gonna be problem?

[jason.greene]

I agree its a bug

[prasad.deshpande]

Jaikiran, Jason, do you want me to create a JIRA for this?

[jaikiran]

Yes please. And if possible attach an example or post the sample code in that JIRA.

[prasad.deshpande]

Created this one https://issues.jboss.org/browse/EJBCLIENT-27

[harisri]

I am using JBOSS EAP 6.4.0, remote client on tomcat getting exact same error. How do we fix this issue?