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

Start node with Timer does not handle versioned deployment

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.4.0.GA
    • 7.1.1.GA
    • jBPM Core
    • None

    • Kieserver
      Deploy 2 versions of a process with a start node on timer

    • Hide

      1. Import this project: https://github.com/dmarrazzo/rhpam71-timer
      2. deploy the master branch
      3. switch to v1.1 branch
      4. deploy the v1.1 branch
      You will notice in the log just this message "v1.0 fired"
      Never the message of the second container.

      Expected behaviour: the newer version should take charge of the timer regardless of the order of deployment.

      E.g.
      process v1.0 deployed
      process v1.1 deployed
      the process v1.1 is started
      otherwise:
      process v1.1 deployed
      process v1.0 deployed
      the process v1.1 is started

      Show
      1. Import this project: https://github.com/dmarrazzo/rhpam71-timer 2. deploy the master branch 3. switch to v1.1 branch 4. deploy the v1.1 branch You will notice in the log just this message "v1.0 fired" Never the message of the second container. Expected behaviour: the newer version should take charge of the timer regardless of the order of deployment. E.g. process v1.0 deployed process v1.1 deployed the process v1.1 is started otherwise: process v1.1 deployed process v1.0 deployed the process v1.1 is started

    Description

      The new version of the process is never triggered: the first activated container control the timer.
      E.g.
      container_1.0 process that starts every 10 seconds
      container_1.1 process that starts every 15 seconds

      the process in container_1.0 is started, the other is never triggered

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPM-7988 EJB timer stops working in specific circumstances

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              elguardian@gmail.com Enrique González Martínez (Inactive)
              dmarrazz@redhat.com Donato Marrazzo
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: