-
Bug
-
Resolution: Done
-
Major
-
None
-
7.0.0.DR9, 7.0.0.ER2 (Beta), 7.0.0.ER4
-
None
During failover testing (EAP 7.0.0.DR9) we've run into the following errors:
2015/08/28 20:53:57:994 EDT [ERROR][Runner - 165] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response! <javax.ejb.EJBException: java.io.IOException: Channel Channel ID 9172b305 (outbound) of Remoting connection 7fec8a5c to perf19/10.16.90.56:8080 has been closed>
javax.ejb.EJBException: java.io.IOException: Channel Channel ID 9172b305 (outbound) of Remoting connection 7fec8a5c to perf19/10.16.90.56:8080 has been closed
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:238)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
at com.sun.proxy.$Proxy0.getNodeName(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.stateless.StatelessSBProcessorFactoryImpl$StatelessEjbRequestProcessor.processRequest(StatelessSBProcessorFactoryImpl.java:92)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Channel Channel ID 9172b305 (outbound) of Remoting connection 7fec8a5c to perf19/10.16.90.56:8080 has been closed
at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:123)
at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:115)
at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:514)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:419)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:290)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:543)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:429)
at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:233)
at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:113)
at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:56)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
... 1 more
I believe this is the same issue as EJBCLIENT-130. The exceptions occur on client side after requests to nodes that have just been shut down/killed. EJBCLIENT-130 is resolved and closed and the fix version is lower than what we have in EAP, so I'll probably have to reopen the issue at some point, but I want to get some more outside input first.
JVM kill and shutdown scenarios are affected. As far as I know, we don't use graceful shutdown in our tests yet, but the issue should be the client not retrying properly after getting an exception (there are other nodes online and ready to handle the request).
- clones
-
-
- Closed
-
- is related to
-
-
- Closed
-
