[jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JBTM-2302:
-----------------------------------------------

Carlo de Wolf <cdewolf at redhat.com> changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from ASSIGNED to MODIFIED

> Tooling can create two mbeans for a CMR record
> ----------------------------------------------
>
>                 Key: JBTM-2302
>                 URL: https://issues.jboss.org/browse/JBTM-2302
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 4.17.23, 5.0.3
>         Environment: JDK8
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 4.17.25, 5.0.4
>
>
> The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because:
> - the record is moved between the locations so there should only ever be one bean representation of it;
> - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model
> The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid.
> The fix is to do the bean remove before adding new beans for new records.
> It is unclear why the bug only happens on JDK8.



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