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

Introduce an API and ability to block suspension of the Recovery Manager until a compatible RecoveryModule has completed it's work

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.Final
    • 7.0.1.Final
    • Transaction Core
    • None
    • Introduced a new functionality into Arjuna to block the suspension of the Recovery Manager when there are transactions to complete/recover

      This issue tracks the introduction of a new functionality into Arjuna to block the suspension of the Recovery Manager when there are transactions to complete/recover. This new feature is essential to complete WFLY-17742. For more details, refer to the related EAP/WFLY issue.

      The API that RecoveryModules need to implement if they need to participate in the ability to prevent suspension can be expected to be:

          /**
           * Called by the RecoveryManager after the completion of the second pass.
           *
           * @return true if there is work left to do, false otherwise
           */
          default boolean hasWorkLeftToDo() {
              return false;
          } 

      This issue will provide a single implementation of the API (AtomicActionRecoveryModule) to validate the API definition is valid however, not all Recovery Modules will be covered by this issue and further modules can expect to be added (or explicitly excluded) via completion of JBTM-3893

              jfinelli@redhat.com Manuel Finelli
              jfinelli@redhat.com Manuel Finelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: