1 Reply Latest reply on May 28, 2015 2:16 AM by Maciej Swiderski

    Start node - timer - old process definition still triggered even if newer process definitions deployed

    Lukasz Dworski Newbie

      Hi,

       

      I have a problem with process definitions versioning.

      I've created a process started with timer with defined cron expression. After latest deployment - that contains newer version of processes - two processes starts at the same time.

      I see in processinstancelog that 2 processes started at the same time, names are equal, only versions are different.

      I want only the newest process to perform - is there any way to force JBPM to trigger only latest process definition?

      My JBPM's version 6.1.0.Final.

       

      I'll appreciate any help.

       

      Luke

        • 1. Re: Start node - timer - old process definition still triggered even if newer process definitions deployed
          Maciej Swiderski Master

          that is expected behavior because deployments in workbench are independent meaning runtime engine does not keep any relationship between them even though it would keep it there is no enough details about what shall be disabled and what not. So engine could not take the decision about disabling start timers as in some case it is desired on others it's not.

           

          So simple solution (though not always possible) is to undeploy old version while deploying new one.

           

          If that is not possible separating processes into different projects might be the way to go. That means you can include processes with start timer events into another project then other processes that change more frequently.

           

          HTH