Details
-
Test
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
5.15.5, 5.15.6
-
None
-
Patch Available
Description
Fix the following tests:
JdbcXARecoveryBrokerTest>CombinationTestSupport.runBare:107->XARecoveryBrokerTest.testPreparedTransactionRecoveredPurgeRollbackOnRestart:332 expected:<0> but was:<4>
JdbcXARecoveryBrokerTest>CombinationTestSupport.runBare:107->XARecoveryBrokerTest.testPreparedTransactionRecoveredPurgeCommitOnRestart:391 null
mKahaDBXARecoveryBrokerTest>CombinationTestSupport.runBare:107->XARecoveryBrokerTest.testPreparedTransactionRecoveredPurgeRollbackOnRestart:332 expected:<0> but was:<4>
mKahaDBXARecoveryBrokerTest>CombinationTestSupport.runBare:107->XARecoveryBrokerTest.testPreparedTransactionRecoveredPurgeCommitOnRestart:391 null
mLevelDBXARecoveryBrokerTest>CombinationTestSupport.runBare:107->XARecoveryBrokerTest.testPreparedTransactionRecoveredPurgeRollbackOnRestart:332 expected:<0> but was:<4>
Those tests are failing because this feature (purge transactions after reboot) was only implemented on the KahaDBPersistenceAdapter.
https://github.com/apache/activemq/commit/ce7498c971b99e2515f07aab36418a1a0f19c03e
The tests are failing because the class XARecoveryBrokerTest is used to test multiples adapters that are not implementing the same feature.
Steps to reproduce:
> git checkout https://github.com/apache/activemq/tree/activemq-5.15.x
> cd activemq-unit-tests
> mvn clean install -Dtest=JdbcXARecoveryBrokerTest
Attachments
Issue Links
- is broken by
-
AMQ-7015 Startup performance improvement when log contains prepared transactions.
- Resolved
- links to