project_key: JBPAPP6 after network restoration, we saw client getting stale data {code} 2012/10/05 08:39:52:617 EDT [WARN ][Runner - 329] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Response serial does not match. Expected: 54, received: 53, runner: 329.> {code} and later {code} 2012/10/05 08:41:54:495 EDT [ERROR][Runner - 129] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.IllegalStateException: EJBCLIENT000028: No EJB receiver contexts available in cluster ejb> java.lang.IllegalStateException: EJBCLIENT000028: No EJB receiver contexts available in cluster ejb at org.jboss.ejb.client.EJBClientContext.requireClusterEJBReceiverContext(EJBClientContext.java:754) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy0.getSerialAndIncrement(Unknown Source) at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75) at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52) at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) at java.lang.Thread.run(Thread.java:662) {code} Cannot find anything on the server side. Link to job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x-failover-ejb-ejbremote-netDown-repl-async/4/
Docs QE Status: Removed: NEW
Affects EAP 6.1.0.ER1. Seen in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Clustering/view/EAP6-Failover/job/eap-6x-failover-ejb-ejbremote-netDown-repl-async/10/console-perf17/
Still here in 6.1.0.ER8: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbremote-netDown-repl-async/17/
Still seeing this in 6.1.1.ER7: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbremote-netDown-repl-async/23/
Just an update: this was seen in 6.2.0.GA as well. Link to sample build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbremote-netDown-repl-async/31/ Link to client log (it's a ~180MB file, I suggest to wget just a part of it, first exception is on line ~1500): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbremote-netDown-repl-async/31/console-perf17/consoleText
The "netDown" scenario should not be used during functional testing. EAP will never handle this scenario perfectly. The attached stacktrace can be expected following this scenario.
Marking for exclusion from Release Notes documentation as not a bug
Hi, I get this error in EAP 6.2. Can you please help me how to fix this?