Uploaded image for project: 'WildFly Transaction Client'
  1. WildFly Transaction Client
  2. WFTC-64

ejb-xa-recovery logs are not being cleared if peer server provides no Xids to recover

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.1.4.Final
    • 1.1.2.Final
    • None

    Description

      If a log file at ejb-xa-recovery crates a SubordinateXaResource whose recover return no Xids, rollback is never invoked and the log file is never cleaned.
      This happens if the peer server containing the remote resource represented by the reloaded SubordinateXaResource no longer contains a pending Xid. This happens, for example, if the server has been restarted or replaced by another server in the same address.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-12090 Unknown service name jboss.ejb and txn

          • 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) WFTC-38 Add active outflowed transaction persistence to JBoss (Narayana) provider

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

          Activity

            People

              flaviarnn Flavia Rainone
              flaviarnn Flavia Rainone
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: