"timfox" wrote : | 8) public void appendRollbackRecord(final long txID) throws Exception | | The bug here is that it doesn't wait for completion of all the transactional operations that came before it. It only waits for completion if the current operation A rollback is actually marking an ignore on the previous transaction with the same id... why do we care about them to complete if the journal is marking all the previous transaction as ignore? Example: Journal is sending 1000 messages on transaction 17. Transaction 17 is marked as rollback while Journal is still processing messaging 300. All the 700 upcoming messages are ignored. On an eventual recovery you would see a rollback anyway.. so I don't think you need to wait all the 700 messages to complete. (At that point you just need to make sure the rollback is serialized on disk) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154319#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...