Uploaded image for project: 'JBoss Enterprise Application Platform 6'
  1. JBoss Enterprise Application Platform 6
  2. JBPAPP6-1490

Domain management API does not expose JTS orphans from the transaction object store



      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.
      Another question is why JBossTS includes orphan filters only for JTA.

      Please consider severity/priority of this issue and discuss the details.

      [1] https://issues.jboss.org/browse/JBQA-5185?focusedCommentId=12684623&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12684623

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  heiko.braun Heiko Braun
                  istudens Ivo Studensky
                • Votes:
                  0 Vote for this issue
                  5 Start watching this issue


                  • Created: