Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-1862

fire TransactionCompletedEvent not as part of the transaction

    XMLWordPrintable

Details

    • Enhancement
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Duplicate Issue
    • 5.1.1.FINAL
    • None
    • Core
    • None

    Description

      When catching TransactionCompletedEvent I would expect, the transaction is committed, especially when isTransactionSuccessful() == true.

      I need to perform some operations after a transaction was completed. My workaround is ATM to suspend the transaction, perform my (async) stuff, and
      resume it afterwards. But in case of errors after resume, I get another TransactionCompletedEvent for this transaction with isTransactionSuccessful() == false.
      You see, I need something like a TransactionReallyCompletedEvent

      My change request is, that the TransactionCompletedEvents should be fired, after the transaction was committed.

      Attachments

        Issue Links

          Activity

            People

              pruivo@redhat.com Pedro Ruivo
              tfromm_jira Thomas Fromm (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: