-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR11
We saw this error on client during most of the ejbremote failover scenarios.
Client log stacktrace:
2017/01/25 13:48:59:083 EST [ERROR][Runner - 169] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <javax.ejb.EJBException: java.util.concurrent.TimeoutException: No invocation response received in 120000 milliseconds>
javax.ejb.EJBException: java.util.concurrent.TimeoutException: No invocation response received in 120000 milliseconds
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.$Proxy2.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84)
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.util.concurrent.TimeoutException: No invocation response received in 120000 milliseconds
at org.jboss.ejb.client.EJBClientInvocationContext$InvocationTimeoutResultProducer.getResult(EJBClientInvocationContext.java:722)
at org.jboss.ejb.client.EJBClientInvocationContext$1.run(EJBClientInvocationContext.java:282)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:279)
at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocationResult(EJBObjectInterceptor.java:64)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocationResult(EJBHomeInterceptor.java:88)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:46)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocationResult(ReceiverInterceptor.java:142)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:265)
at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:453)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:204)
... 7 more
2017/01/25 13:48:59:093 EST [INFO ][Runner - 169] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Reached treshold of 1 errors, resetting session.
Occured after cluster-wide rebalance finished. Server logged at the same time:
13:48:08,191 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t87) ISPN000336: Finished cluster-wide rebalance for cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar, topology id = 22
Scenarios affected:
eap-7x-failover-ejb-ejbremote-jvmkill-dist-async
eap-7x-failover-ejb-ejbremote-jvmkill-repl-async
eap-7x-failover-ejb-ejbremote-jvmkill-repl-sync
eap-7x-failover-ejb-ejbremote-shutdown-dist-async
eap-7x-failover-ejb-ejbremote-shutdown-dist-sync
eap-7x-failover-ejb-ejbremote-shutdown-dist-sync-3owners
eap-7x-failover-ejb-ejbremote-shutdown-repl-async
eap-7x-failover-ejb-ejbremote-undeploy-repl-async
Link to client log:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-ejb-ejbremote-jvmkill-dist-async/9/console-perf17/
- is blocked by
-
JBEAP-9355 EJB cluster proxies are not failing over
-
- Closed
-