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

(7.4.z) Unsupported Transaction Recovery Scenarios

    XMLWordPrintable

Details

    Description

      Section "9.15.1. Unsupported Transaction Recovery Scenarios" has been removed
      by mistake. In fact, both JTS and XTS protocols still need to be tested wrt compatibility (using the EAP operator)
      In particular, the XTS caveat in this section still applies as far as the transaction team knows (certain issue https://issues.redhat.com/browse/JBTM-2742 was a blocker and not fixed). So too much has been removed from the docs.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-23200 Documentation no longer covers unsupported transaction recovery topics on OpenShift

          • 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 caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19128 Remove OpenShift Legacy transaction Recovery approach from documentation

          • 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-23569 [7.4] Fix link to Unsupported Transaction Recovery Scenarios in OpenShift guide

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              thjenkin@redhat.com Tom Jenkinson
              jfinelli@redhat.com Manuel Finelli
              Martin Choma Martin Choma
              Martin Choma Martin Choma
              Darragh Fitzmaurice, Satyajeet Munje, Sreelatha Nelluli
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: