Details

    • Type: Bug Bug
    • Status: Ready for QA Ready for QA (View Workflow)
    • Priority: Normal Normal
    • Resolution: Unresolved
    • Component/s: SRD
    • Labels:
      None Labels
    • Customer:
      OMAN-Tel
    • Product:
      NEP

      Description

      Dear support, Kinly check why solution not highlighted in request 2201

        Activity

        Hide
        Abir Messaikeh added a comment -

        as workaround we asked the user to make a start over

        Show
        Abir Messaikeh added a comment - as workaround we asked the user to make a start over
        Hide
        Ayed Bada added a comment -

        During execution of the SRD process (attached BPMN), i observed the following error:
        ORA-00001: unique constraint (SRD_PROD.SYS_C0063096) violated
        Root Cause:
        This issue occurs in the parallel multi-instance call activity due to a concurrency conflict when Flowable tries to insert multiple activity instances into the database at the same time.
        The problem is intermittent and does not happen on every execution.
        Under high traffic or simultaneous execution, multiple parallel instances may attempt to insert the same activity instance ID, triggering the unique constraint violation.
        When the process is restarted (“Start over”), it usually completes successfully because the timing of the parallel inserts differs, avoiding the collision.
        Solution:
        Remove flowable:completeAsync="true" from the call activity to prevent the activity scope from being completed asynchronously.
        This ensures the multi-instance inserts happen within the same transaction context, eliminating the race condition.

        Show
        Ayed Bada added a comment - During execution of the SRD process (attached BPMN), i observed the following error: ORA-00001: unique constraint (SRD_PROD.SYS_C0063096) violated Root Cause: This issue occurs in the parallel multi-instance call activity due to a concurrency conflict when Flowable tries to insert multiple activity instances into the database at the same time. The problem is intermittent and does not happen on every execution. Under high traffic or simultaneous execution, multiple parallel instances may attempt to insert the same activity instance ID, triggering the unique constraint violation. When the process is restarted (“Start over”), it usually completes successfully because the timing of the parallel inserts differs, avoiding the collision. Solution: Remove flowable:completeAsync="true" from the call activity to prevent the activity scope from being completed asynchronously. This ensures the multi-instance inserts happen within the same transaction context, eliminating the race condition.
        Hide
        Abir Messaikeh added a comment -

        pending stress test or further tests for variable on staging b4 apply new process on PROD

        Show
        Abir Messaikeh added a comment - pending stress test or further tests for variable on staging b4 apply new process on PROD

          People

          • Assignee:
            Abir Messaikeh
            Reporter:
            Abir Messaikeh
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 4 hours
              4h

                Drag and Drop