In Glassfish, a TransactionListener is invoked after Transaction is committed

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Won't Fix
    • Priority: L3 - Default
    • None
    • Affects Version/s: 7.3.7, 7.4.8
    • Component/s: engine
    • None
    • Environment:
      Glassfish

      Given:

      • an async ServiceTask which is implemented as JavaDelegate
      • inside the Delegate, a TransactionListener is registered for state Committing which throws an exception

      When:

      • the job executor executes the delegate

      Then:

      • the TransactionListener is invoked and throw an exception
      • but the job is marked as successful and the process continues

      Hint:

      • it seems that the transaction is already committed when the TransactionListener is invoked (job entity is already deleted)
      • expected behavior in camunda > 7.4
      • see engine integration test AsyncJobExecutionTransactionListenerTest

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Philipp Ossler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: