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

Clustered EJB timers start duplicated process instances when used inside startEvent

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.3.0.Final
    • Fix Version/s: 7.5.0.Final
    • Component/s: Runtime Engine
    • Labels:
      None
    • Environment:

      EAP 7.0.8
      MySQL 5.7 / PostgreSQL 9.5

    • Sprint:
      2017 Week 40-41-42
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      The clustered EJB timers seem to be misbehaving in case the timer is used to start new process instances via the startEvent. After talking to Maciej Swiderski and Karel Suta the expected behavior is that the different engine instances (inside different kie-servers) should cope with this, and only one of them should fire the timer. Current behavior is that both (or more) kie-server instances fire the timers.

      This issue was observed in kie-server, but it probably is not limited to that.

        Gliffy Diagrams

          Attachments

          1. standalone.xml
            25 kB
          2. timer.bpmn2
            8 kB

            Issue Links

              Activity

                People

                • Assignee:
                  swiderski.maciej Maciej Swiderski
                  Reporter:
                  psiroky Petr Široký
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: