Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-2983

Check if transaction is active before performing save operations

    XMLWordPrintable

Details

    Description

      If task ending is unsuccessful, the BusinessProcessInterceptor.afterInvocation method will close the JbpmContext.

      However, there is an issue with jBPM auto-save operations, which complain about the transaction not being active and throw an exception. The exception in fact comes from Hibernate.

      jBPM should check whether the transaction is active before proceeding to perform the auto-save operations.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5517 Seam exception and transaction handling in JBPM integration is not correct for failed EL expression evaluation

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPM-3883 Fix for JBPM-2983 broke externally managed transactions support

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              aguizar_jira Alejandro Guizar (Inactive)
              mnovotny@redhat.com Marek Novotny
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 hours Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 5 hours, 16 minutes
                  5h 16m