The issue was related to the time-components on the IDs for sure. I added a test PreserveOrderDuringFailoverTest, which is based on AutomaticFailoverWithDiscoveryTest. If you uncomment some code on PreserveOrderDuringFailoverTest, this issue will aways happen: // This test would fail if both servers have the same time component | // NullStorageManager storageManagerLive = (NullStorageManager)liveService.getServer().getStorageManager(); | // TimeAndCounterIDGenerator idgeneratorlive = (TimeAndCounterIDGenerator)storageManagerLive.getIDGenerator(); | // | // NullStorageManager storageManagerBackup = (NullStorageManager)backupService.getServer().getStorageManager(); | // TimeAndCounterIDGenerator idgeneratorBackup = (TimeAndCounterIDGenerator)storageManagerBackup.getIDGenerator(); | // | // idgeneratorBackup.setInternalDate(0); | // idgeneratorlive.setInternalDate(0); | I would expect the IDs not affecting failover any more, so I would debug this but since this part is already changed at Tim's workspace, I will leave this alone. Tim: If you could please remove the wait on FailoverTestBase during your commit. Since you have changed the ID logic, we won't need the wait any more. | backupService.start(); | | - Thread.sleep(20); | | Configuration liveConf = new ConfigurationImpl(); | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219995#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...