Bug 779227 (SOA-1620)

Summary: Backport JBMESSAGING-1439 to SOA-P 4.3
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Taro Yasuma <tyasuma>
Component: JBoss MessagingAssignee: Darran Lofthouse <darran.lofthouse>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 CP02CC: dlesage
Target Milestone: ---   
Target Release: 4.3 CP04 CR2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1620
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-12 08:32:21 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Deadline: 2010-03-08   

Description Taro Yasuma 2009-11-20 05:44:09 UTC 
Date of First Response: 2010-02-25 11:43:41
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/303780
project_key: SOA

See JBPAPP-3131.
Comment 1 Taro Yasuma 2009-11-20 05:46:32 UTC 
Link: Added: This issue depends JBPAPP-3131
Comment 2 Anne-Louise Tangring 2010-02-25 16:43:41 UTC 
Approved for SOA 4.3 CP03, but is dependent on inclusion into EAP 4.3 CP08 and the ability to include EAP 4.3 CP08 into SOA 4.3 CP03 per schedule.
Comment 3 David Le Sage 2010-04-09 00:23:01 UTC 
Documented as Known Issue in current draft of Release Notes. Will be moved to "Resolved Issues" section if fixed before release:



SOA-1620 https://jira.jboss.org/jira/browse/JBPAPP-3131

   There is a need to backport JBMessaging-1439 because it allows a user to list all prepared XA
   (distributed global) transactions. This information can be used to help in decisions to commit or
   rollback transactions if there has been a problem with the system.

   There is no work-around for this lack of functionality.
Comment 4 Jiri Pechanec 2010-05-12 08:32:21 UTC 
Verified in CR2 - SOA-P is based on EAP 4.3 CP08 GA