Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2850

Call xa_end on duplicate XAResource as per JTA 1.2 specification

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 5.5.5.Final
    • Component/s: JTA
    • Labels:
      None

      Description

      JTA 1.2 changed requirement:

      "A transaction manager is, however, required to implicitly ensure the association of any associated XAResource is ended, via the appropriate XAResource.end call, immediately prior to completion;"

      The change is that it no longer is confined to any associated ** resource **, but now specifies any associated ** XAResource **

      What is happening at the moment for two difference instance of an XAR but where isSameRM is true:
      Resource1 start TMNOFLAGS
      DuplicateResource1 start TMJOIN
      Resource2 start TMNOFLAGS
      Resource1 end TMSUCCESS
      Resource1 prepare
      Resource2 end TMSUCCESS
      Resource2 prepare
      Resource1 commit
      Resource2 commit

      Post https://java.net/jira/browse/JTA_SPEC-3 this should be:
      Resource1 start TMNOFLAGS
      DuplicateResource1 start TMJOIN
      Resource2 start TMNOFLAGS
      Resource1 end TMSUCCESS
      DuplicateResource1 end TMSUCCESS
      Resource1 prepare
      Resource2 end TMSUCCESS
      Resource2 prepare
      Resource1 commit
      Resource2 commit

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tomjenkinson Tom Jenkinson
                  Reporter:
                  tomjenkinson Tom Jenkinson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: