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

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 5.5.5.Final
    • None
    • JTA
    • 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

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8088 [GSS](7.2.0) XA resource with same RMid are not ended properly

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-6843 [EAP] [GSS](7.2.0) Artemis is not fully-JTA 1.2 compliant XAResource

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Backlog

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9505 [GSS](7.4.z) Artemis is not fully-JTA 1.2 compliant XAResource

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12671 [GSS](7.1.z) Artemis is not fully-JTA 1.2 compliant XAResource

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2128 [GSS](7.2.0) Artemis is not fully-JTA 1.2 compliant XAResource

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link is caused by JTA_SPEC-3

          Activity

            People

              thjenkin@redhat.com Tom Jenkinson
              thjenkin@redhat.com Tom Jenkinson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: