[jboss-jira] [JBoss JIRA] (WFLY-3613) Domain management API does not expose JTS orphans from the transaction object store

[Ivo Studensky (JIRA)]

Ivo Studensky created WFLY-3613:
-----------------------------------

             Summary: Domain management API does not expose JTS orphans from the transaction object store
                 Key: WFLY-3613
                 URL: https://issues.jboss.org/browse/WFLY-3613
             Project: WildFly
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: Domain Management, Transactions
    Affects Versions: 8.1.0.Final
            Reporter: Ivo Studensky
            Assignee: Ivo Studensky


At the moment domain management API exposes transactions and their participants from the object store. Thus it is possible to traverse down from a transaction to its participant records which is nice.

However in special cases it is possible to create "orphan" records in the object store, i.e. XAResourceRecord's which do not have any corresponding transaction record in the log (e.g. XA resource prepared but crashed before the TM recorded the fact) and thus are inaccessible for the domain management API, see [1]. In case of JTA it is not very problem as JBossTS has orphan filters for JTA that can remove such orphans automatically. But in case of JTS this becomes to be a problem as JBossTS does not have any orphan filers for JTS and the orphan records stay in the object store. Because of this we would need a tool that can expose and remove such records at least for HornetQ based object store where it is not possible to remove them manually from the file system.




--
This message was sent by Atlassian JIRA
(v6.2.6#6264)