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

Recovery Support in Compensation API

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Compensations
    • None

    Description

      Background
      Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers will be invoked in case of the system crash.

      Requirements

      1. Make handlers persistable (CompensationHandler, ConfirmationHandler, TransactionLoggedHandler).
        1. Require Serializable interface.
        2. Create PersistableHandler interface (similar to PersistableParticipant in RTS integration).
      2. Make participant persistable (ParticipantImpl, LocalParticipant, RemoteParticipant).
        1. Make transaction identifier persistable (converting it to String should work).
        2. Implement PersistableParticipant in ParticipantImpl.
        3. Investigate if PARTICIPANT_COUNTERS in ParticipatnImpl have to be updated.
      3. Make compensation scoped beans persistable.

      Attachments

        Issue Links

          is blocked by

          Task - Represents a small unit of work that is not end-user facing. JBTM-2782 XTS crash recovery test Byteman rules use wrong variable types

          • 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

          Task - Represents a small unit of work that is not end-user facing. WFLY-7304 Compensations subsystem

          • 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
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBTM-2794 Javadoc compensations framework

          • 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.
          • Reopened

          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) WFLY-11421 Correct the compensations framework dependency to be for the XTS subsystem

          • 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

              Unassigned Unassigned
              thjenkin@redhat.com Tom Jenkinson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: