]
Ivo Studensky commented on JBTM-1231:
-------------------------------------
This issue affects JTA distributed transactions (via EJB Remoting).
Recovery not fully triggered when distributed transaction falls down
at prepare phase of 2PC
--------------------------------------------------------------------------------------------
Key: JBTM-1231
URL:
https://issues.jboss.org/browse/JBTM-1231
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Recovery, Testing
Affects Versions: 4.16.4
Reporter: Ivo Studensky
Assignee: Tom Jenkinson
Attachments: logs_prepareHaltClient.tgz
It looks like recovery process is not fully triggered on a distributed transaction when
the transaction falls down at prepare phase of 2PC. In the new crash recovery tests over
propagated transactions only one of two servers recovers from the crash, but the other
keeps an unfinished tx in its tx log.
It corresponds to prepareHaltClient and prepareHaltServer test methods of
org.jboss.as.test.jbossts.crashrec.txpropagation.TxPropagationCrashRecoveryTestCase, see
JBQA-2604 for general description of the new tests. The prepareHaltClient test crashes the
server which initiated the transaction, while as the prepareHaltServer test crashes the
second server.
The tests are written against EAP6.x branch, so for reproducing this it is needed a built
server from the 7.1 branch of AS7.
Steps to reproduce.
1. git clone
git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-transactions.git
2. cd eap-tests-transactions
3. git checkout tx_propag_crashrec_tests
4a. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltClient
-Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT>
or
4b. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltServer
-Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT>
The logs of prepareHaltClient run attached to this jira.
Tom, could you take a look at this please?
Thanks a lot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: