[jbosscache-issues] [JBoss JIRA] Updated: (JBCACHE-1445) Data gravitation cleanup does not happen when using single-phase commits.

[ https://jira.jboss.org/jira/browse/JBCACHE-1445?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1445: ----------------------------------- Summary: Data gravitation cleanup does not happen when using single-phase commits. (was: Problem with cleanup after data gravitation) Description: This includes using transactions or invocation batching with asynchronous replication. From Brian's original analysis: "JBoss AS web session replication soak testing is showing issues with buddy replication. One of the failure modes seems to show leftover data remaining in the main tree for a session's former owner after the session has failed over to another node. I've taken this issue as a good chance to start filling in the test infrastructure in the org.jboss.cache.integration package. Test org.jboss.cache.integration.websession.BuddyReplicationFailoverTest.testFailoverAndFailBack() shows the issue. I think some of the tests in the buddyreplication package should be checking for this; not sure why they pass. Likely some subtle variation in config or something. The test uses a lot of infrastructure to mock what the AS does. But underneath it all, the commands to the cache come down to: node0: getData(fqn) w/ data gravitation option // nothing there put(fqn, map) // establishes session put(fqn, map) // updates session node3 getData(fqn) w/ data gravitation option // gravitates session put(fqn, map) // updates session At this point the cache contents are examined, and the original node in node0's main tree is still present. A buddy backup node, data owner node3, is also present on node0, as it should be." was: JBoss AS web session replication soak testing is showing issues with buddy replication. One of the failure modes seems to show leftover data remaining in the main tree for a session's former owner after the session has failed over to another node. I've taken this issue as a good chance to start filling in the test infrastructure in the org.jboss.cache.integration package. Test org.jboss.cache.integration.websession.BuddyReplicationFailoverTest.testFailoverAndFailBack() shows the issue. I think some of the tests in the buddyreplication package should be checking for this; not sure why they pass. Likely some subtle variation in config or something. The test uses a lot of infrastructure to mock what the AS does. But underneath it all, the commands to the cache come down to: node0: getData(fqn) w/ data gravitation option // nothing there put(fqn, map) // establishes session put(fqn, map) // updates session node3 getData(fqn) w/ data gravitation option // gravitates session put(fqn, map) // updates session At this point the cache contents are examined, and the original node in node0's main tree is still present. A buddy backup node, data owner node3, is also present on node0, as it should be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira