Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1168973 - JTS participants are not showing up in the tooling
JTS participants are not showing up in the tooling
Status: VERIFIED
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager (Show other bugs)
6.4.0
Unspecified Unspecified
unspecified Severity medium
: ER1
: EAP 6.4.0
Assigned To: Michael
Hayk Hovsepyan
:
Depends On:
Blocks: 1176841
  Show dependency treegraph
 
Reported: 2014-11-28 10:13 EST by Hayk Hovsepyan
Modified: 2018-03-06 15:40 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
This release of JBoss EAP 6 contains an enhancement to the Transaction Manger component. Previously, not all particpants were appearing in the log viewer. Now, the following types of participants will be shown: * AssumedCompleteHeuristicTransaction * AssumedCompleteHeuristicServerTransaction * AssumedCompleteTransaction * AssumedCompleteServerTransaction
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker JBTM-2308 Major Closed New JTS record types are not showing up in the tooling 2017-09-22 08:34 EDT
JBoss Issue Tracker WFLY-4164 Major Resolved New JTS record types are not showing up in the CLI 2017-09-22 08:34 EDT

  None (edit)
Description Hayk Hovsepyan 2014-11-28 10:13:38 EST
When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record.

This BZ was raised while verifying https://bugzilla.redhat.com/show_bug.cgi?id=1080140 as tooling does not show participants of the JTS record.
Comment 1 Hayk Hovsepyan 2014-11-28 10:15:03 EST
Created as a BZ representation of JBTM-2308
Comment 2 JBoss JIRA Server 2014-12-23 08:20:51 EST
Michael Musgrove <mmusgrov@redhat.com> updated the status of jira JBTM-2308 to Reopened
Comment 3 JBoss JIRA Server 2014-12-23 09:07:50 EST
Michael Musgrove <mmusgrov@redhat.com> updated the status of jira JBTM-2308 to Resolved
Comment 4 tom.jenkinson 2014-12-23 10:12:05 EST
https://github.com/jbossas/jboss-eap/pull/2184
Comment 5 Hayk Hovsepyan 2015-01-12 11:02:45 EST
Verified on revision EAP 6.4.0 ER1
Comment 6 JBoss JIRA Server 2015-05-01 09:37:15 EDT
Tom Jenkinson <tom.jenkinson@redhat.com> updated the status of jira JBTM-2308 to Closed
Comment 7 JBoss JIRA Server 2015-06-05 04:08:50 EDT
Michael Musgrove <mmusgrov@redhat.com> updated the status of jira JBTM-2308 to Reopened
Comment 8 JBoss JIRA Server 2015-06-09 09:19:41 EDT
Michael Musgrove <mmusgrov@redhat.com> updated the status of jira JBTM-2308 to Resolved
Comment 9 JBoss JIRA Server 2015-06-17 08:19:17 EDT
Michael Musgrove <mmusgrov@redhat.com> updated the status of jira JBTM-2308 to Reopened
Comment 10 JBoss JIRA Server 2015-06-23 05:49:26 EDT
Michael Musgrove <mmusgrov@redhat.com> updated the status of jira JBTM-2308 to Resolved
Comment 11 JBoss JIRA Server 2015-07-08 05:17:31 EDT
Tom Jenkinson <tom.jenkinson@redhat.com> updated the status of jira JBTM-2308 to Closed
Comment 12 JBoss JIRA Server 2015-07-13 03:03:15 EDT
Tom Jenkinson <tom.jenkinson@redhat.com> updated the status of jira WFLY-4164 to Resolved

Note You need to log in before you can comment on or make changes to this bug.