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

Clarify what is situation when "The transaction log might not be cleared" under section Limitations of the XA Recovery Process

    Details

    • Type: Bug
    • Status: New (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.0.0.GA, 7.1.0.GA
    • Fix Version/s: None
    • Component/s: Documentation
    • Labels:
      None

      Description

      The chapter Limitations of the XA Recovery Process (11.2.10. in EAP 7.1, Revised on 2017-12-05 13:54:45 EST) contains section The transaction log might not be cleared from a successfully committed transaction which is not much precise in what it talks about.

      Link: https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.1/html-single/development_guide/index#limitations_of_the_xa_recovery_process

      This section was created for EAP 6.4 documentation because of not fixed bug https://issues.jboss.org/browse/JBTM-860. That's not true from release 7.0 and it should be mentioned what are the real limitations now.

      I think the text could be something like (please rephrase this to be more understandable)

      If the JBoss EAP server crashes after an XAResource commit method successfully completes and commits the transaction, but before the coordinator can update the log, you may see the following warning message in the log when you restart the server:

      ARJUNA016037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord

      This warnings could not be seen from release of JBoss EAP 7.0.0 where was implemented a procedure (https://issues.jboss.org/browse/JBTM-860) dealing with this issue. But there is necessary a cooperation from implementation of the XAResource to provide identifier for transaction manager understanding what is the origin of the in-doubt record and then it could decide if transaction participant was or wasn't committed.

      The limitation does not affect

      • any datasource - database jdbc connection - configured in WildFly
      • artemis activemq resource adapter - messaging-activemq WildFly configuration

      This limitation does affect

      • any 3rd party resource adapter (e.g. WSMQ) where implementation of XAResourc does not implement interface org.jboss.tm.XAResourceWrapper

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  nids1409 Nidhi Chaudhary
                  Reporter:
                  ochaloup Ondrej Chaloupka
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated: