Bug 1146450

Summary: Some in-doubt txs still left in the database.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Hayk Hovsepyan <hhovsepy>
Component: Transaction ManagerAssignee: Gytis Trikleris <gtrikler>
Status: CLOSED DUPLICATE QA Contact: Hayk Hovsepyan <hhovsepy>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.4.0CC: ochaloup, tom.jenkinson
Target Milestone: ---   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-07 13:46:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hayk Hovsepyan 2014-09-25 09:39:01 UTC 
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
Comment 4 Gytis Trikleris 2014-10-07 13:46:43 UTC 
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 ***