Description of problem: When using several XA resources and a CMR resource in a transaction, then after server is crashed and recovery (3 times) is called, there is still some in-doubt transaction in logs. Version-Release number of selected component (if applicable): 6.4.0.DR2 How reproducible: always Steps to Reproduce: 1. Define 2 XA resource, 1 TestXA resource and 1 CMR resource in transaction. 2. Crash at prepare method entry of TestXAResource. 3. Reboot the server and call recovery 3 times. 4. Check that there is still an unfinished Xid on server. Actual results: 1 in-doubt Xid left Expected results: no any in-doubt Xids should left after 3x recovery Additional info: Similar issue was fixed for 6.4.0 but with different scenario:https://bugzilla.redhat.com/show_bug.cgi?id=1075086 Possibly this BZ can be related to https://bugzilla.redhat.com/show_bug.cgi?id=1104227
During the rollback of CrashRecoveryDS2 resource, JCA uses JNDI name of CrashRecoveryDS1. This causes the following exception (and failure to rollback the transaction): "java.sql.SQLException: ORA-24774: cannot switch to specified transaction". This is a JCA issue and is documented here: https://bugzilla.redhat.com/show_bug.cgi?id=1104227 *** This bug has been marked as a duplicate of bug 1104227 ***