Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-6751

In Glassfish, a TransactionListener is invoked after Transaction is committed

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Won't Fix
    • L3 - Default
    • None
    • 7.3.7, 7.4.8
    • engine
    • None
    • Glassfish

    Description

      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

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Bug Report - A problem which impairs or prevents the functions of the product. CAM-3303 Job/incident exception message is not populated when exception is from a transaction synchronization

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Activity

              People

                Unassigned Unassigned
                philipp.ossler Philipp Ossler
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce