[ https://issues.jboss.org/browse/WFLY-10024?page=com.atlassian.jira.plugin... ] tommaso borgato updated WFLY-10024: ----------------------------------- Description: Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication) When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side: {code:java} 2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597 at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133) 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:748) {code} Looks like this bug is related to a previous one marked as VERIFIED : https://issues.jboss.org/browse/WFLY-6225 Full log : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f... was: Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication) When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side: {code:java} 2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597 at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133) 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:748) {code} Looks like this bug is related to a previous one marked as VERIFIED : https://issues.jboss.org/browse/WFLY-6225 Complete logs : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f... -- This message was sent by Atlassian JIRA (v7.5.0#75005)