Details
Description
This bug produces a few errors on the client (standalone EJB client v4).
Errors are about 20 in whole test so Priority can stay Major.
Nevertheless, the error happens in clean shut down scenario which should be as smooth as possible.
The error is directly related to fail-over (e.g. clean shutdown) and appears immediately after the first node (of a 4 nodes cluster) is failed.
ClosedChannelException started to occur on client during clustering failover scenarion ejb-ejbremote-jvmkill-dist-sync immediately after one of the nodes (perf18) left the cluster.
Client log stacktrace:
2017/08/31 08:43:39:182 EDT [ERROR][Runner - 1049] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <javax.ejb.EJBException: java.nio.channels.ClosedChannelException>
javax.ejb.EJBException: java.nio.channels.ClosedChannelException
at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleClosed(EJBClientChannel.java:1094)
at org.jboss.remoting3.util.InvocationTracker.connectionClosed(InvocationTracker.java:222)
at org.jboss.remoting3.util.InvocationTracker.lambda$new$0(InvocationTracker.java:70)
at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:50)
at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:508)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:413)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:286)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:508)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:368)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:621)
at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:121)
at org.jboss.remoting3.remote.RemoteReadListener.lambda$null$0(RemoteReadListener.java:54)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.channels.ClosedChannelException
... 16 more
The errors were logged several times until
2017/08/31 08:43:43:268 EDT [ERROR][Runner - 1208] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Lookup failed: javax.naming.CommunicationException: EJBCLIENT000062: Failed to look up "clusterbench-ee7/clusterbench-ee7-ejb//RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB?stateful" [Root exception is javax.ejb.CreateException: Failed to create stateful EJB: Connection refused]
There wa no erro logged on server at that time.
Link to client log:
https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-ejb-ejbremote-jvmkill-dist-sync/31/console-perf17/
Attachments
Issue Links
- is incorporated by
-
JBEAP-16566 [GSS](7.2.z) XNIO-336 - Socket accept error should log at ERROR level before closing the channel
-
- Verified
-
