Description of problem: dtx Rollback does not preserve message order. How reproducible: The test testMultiMessagesDurSubCrash from org.apache.qpid.test.unit.xa.TopicTest exhibits this behavior. The following profile should be used: --------------------------------------------------------- broker.version=0-10 broker=${project.root}/../cpp/src/qpidd --data-dir ${build.data} -t --load-module ${project.root}/../../cppStore/cpp/lib/.libs/libbdbstore.so --store-async yes --auth no broker.clean=${project.root}/clean-dir ${build.data} java.naming.provider.url=${project.root}/test-provider.properties max_prefetch=0 test.excludes=true test.excludesfile=${project.root}/myExcludeList log=info amqj.logging.level=$log root.logging.level=$log log4j.configuration=file://${project.root}/log4j-test.xml test.fork=no test.mem=512M test=*TopicTest test1=*TopicTest haltonfailure=no haltonerror=no ------------------------------------------------------------------ Where myExcludeList contains: ------------------------------------ org.apache.qpid.test.unit.xa.TopicTest#testMigrateDurableSubscriber org.apache.qpid.test.unit.xa.TopicTest#testDurSub org.apache.qpid.test.unit.xa.TopicTest#testDurSubCrash org.apache.qpid.test.unit.xa.TopicTest#testMultiMessagesDurSub org.apache.qpid.test.unit.xa.TopicTest#testProducer org.apache.qpid.test.unit.xa.TopicTest#testRecover -------------------------------------
The incriminated test does not run on CC. We must enable it before closing this bug.
This is an issue with the way recovery works in the broker.