Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2120

Recover if a transaction is in progress but a JTA Synchronization callback cannot be registered

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 2.3.4.Final, 3.0.0.Alpha16
    • None
    • Events
    • None

    Description

      This might happen e.g. if an event is fired after the transaction is marked for rollback. We should catch javax.transaction.RollbackException and java.lang.IllegalStateException (I'm not sure about javax.transaction.SystemException) and notify all transactional observers immediately, except for observers with TransactionPhase.AFTER_SUCCESS (these should be ignored).

      See also CDI-578 and OWB-1111.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. WELD-2132 Clarify TransactionServices.registerSynchronization() contract

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

          Activity

            People

              tremes1@redhat.com Tomas Remes
              mkouba@redhat.com Martin Kouba
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: