[jboss-jira] [JBoss JIRA] (WFLY-10024) Stale data

tommaso borgato (JIRA) issues at jboss.org
Wed Mar 14 13:18:00 EDT 2018


tommaso borgato created WFLY-10024:
--------------------------------------

             Summary: Stale data
                 Key: WFLY-10024
                 URL: https://issues.jboss.org/browse/WFLY-10024
             Project: WildFly
          Issue Type: Bug
          Components: Clustering
    Affects Versions: 13.0.0.Beta1
            Reporter: tommaso borgato
            Assignee: Paul Ferraro


WildFly Full 13.0.0.Alpha1-SNAPSHOT
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)

When the node failover 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




--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list