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

Add orphan detection for JTS interposition mode

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • 4.17.17
    • Recovery
    • None

    Description

      Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well.

      The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms.

      The program flow is following (test run on EAP 6)
      enlisting jms xaresource to transaction
      sending msg to queue
      enlisting xa test resource
      preparing jms xaresource
      preparing xa test resource
      crash JVM at the end of the test XAResource.prepare()
      restart app server and recovery is run

      During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback.

      More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-2287 JTS mode sends an erroneous xa_end to resource manager if prepare() returns RMFAIL

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-2893 JTS subordinate transaction could check Xid format during enlistment to allow it being edited

          • 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
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-2583 Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

          • 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

          Activity

            People

              Unassigned Unassigned
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: