Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-2122

If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.0.0.ER4
    • 7.0.0.ER3
    • Transactions
    • None

    Description

      Cloned from JBTM-2569 - based on Tom's investigation:

      During investigation of https://issues.jboss.org/browse/JBEAP-1750
      it was discovered that there exists an issue in XARecoveryModule where
      if the object store transaction log check throws an exception during
      orphan detection then the record is treated as if it does not have a
      log.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBTM-2569 If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-2267 Upgrade Narayana to 5.2.9.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1750 Stuck server when stopped right after started if jdbc store for transaction logs is used

          • 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

              thjenkin@redhat.com Tom Jenkinson
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Ondrej Chaloupka Ondrej Chaloupka (Inactive)
              Ondrej Chaloupka Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: