[jbossts-issues] [JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling

[Michael Musgrove (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023690#comment-13023690 ] 

Michael Musgrove commented on JBTM-2308:
----------------------------------------

I have removed 4.17.x from the fix versions since I won't have time to fix it for tomorrows release. I will work on it for the one after that.

The problem is that JTS participant records are not stored in-line with the owning transaction (in contrast to JTA). If I show participants as children of the owning transaction then when expose all logs is enabled we would end up creating two representations of the participant (one under CosTransactions/XAResource and the other under the JTS transaction record node). This would break on wildfly since we use the record Uid as the id of the wildfly model node and duplicate ids are not allowed. 

> JTS participants are not showing up in the tooling
> --------------------------------------------------
>
>                 Key: JBTM-2308
>                 URL: https://issues.jboss.org/browse/JBTM-2308
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 4.17.23, 5.0.3
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.4
>
>
> 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.
> I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time).



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)