Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-3929

Duplicate timer creation in multi-node setup

    XMLWordPrintable

Details

    • Bug
    • Status: Verified (View Workflow)
    • Critical
    • Resolution: Done
    • 7.11.1.GA
    • 7.12.1.GA
    • jBPM Core
      • 2 kie-server nodes
      • EJB timers with DB persistence
    • CR1
    • Hide

      see attached reproducer

      Show
      see attached reproducer
      • lowering the refresh-interval of the EJB timer DB configuration reduces the likelihood of this issue to occur
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • 2021 Week 40-42 (from Oct 4), 2021 Week 43-45 (from Oct 25), 2021 Week 46-48 (from Nov 15), 2021 Week 49-51 (from Dec 6th), 2022 Week 02-04 (from Jan 10)
    • ?

    Description

      In a setup with multiple kie-server nodes, the following sequence of actions can lead to duplicate EJB timer instances getting created:

      1. Start a process instance containing a timer on node1
      2. Access the newly created process instance on node2 (eg. REST call to retrieve variables)

      If the call in step #2 happens before the EJB timers are synced at the EAP layer (wait time < refresh-interval), then RHPAM will create a second EJB timer instance during the session initialization.

       
      Note: this issue is similar to the scenario tracked in JBEAP-22092, but for a slightly different use case.

      Attachments

        Issue Links

          Activity

            People

              elguardian@gmail.com Enrique González Martínez (Inactive)
              rhn-support-mputz Martin Weiler
              Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: