2 Replies Latest reply on Nov 2, 2012 5:39 AM by amadets

    jbpm 5.3 and Timer Intermediate Event

    amadets

      Hi,

      I have a process that is shown in the following figure:

      timer.png

      Case 1

      When I start process the engine creates a "task 1".

      The engine also creates the timer with attribute set: Time Duration = 10000ms and CancelActivity = true.

      Everything is saved to the database.

      After 10 seconds the engine shuts "task 1" and sets the status "Exited" and creates a "task 2".

      And everything is in order.

      Case 2

      When I start process the engine creates a "task 1"

      The engine also creates the timer with attribute set: Time Duration = 10000ms and CancelActivity = true.

      Everything is also saved to the database.

      Before 10 seconds I close the application (kill jboss) and run again.

       

       

      Why Timer does not work anymore?

      What do I do with the application to start the timer started?

       

      There is a bug:

      https://issues.jboss.org/browse/JBPM-3170

      https://bugzilla.redhat.com/show_bug.cgi?id=869289

       

       

      please any tips

      ts

        • 1. Re: jbpm 5.3 and Timer Intermediate Event
          m_arnold123

          Hi amadets,

           

          jBPM5 is not very friendly when it comes to timers :-(  All your sessions have to be loaded from persistence for their timers to expire. So it is up to you to write some special code to load all your sessions when JBoss starts.

           

          More information here:

          https://community.jboss.org/thread/204007

          https://community.jboss.org/thread/211785

          • 2. Re: jbpm 5.3 and Timer Intermediate Event
            amadets

            Hi, I've been absent

            After reading this https://community.jboss.org/thread/211785 i have idea:

             

            I have about 500,000 active instances of processes. Each instance of the process is supported by a single session.

            loadStatefulKnowledgeSession (...) from database takes 150ms.

            After restart AS is: 500 000 * 0,15 / 60 / 60 is about 20 hours. This is a joke

             

            6 years ago in jbpm 3.2.2 was simple mechanism with one table in the database and select to them every 1 second. Simple but very effective.

            Today we have version 5.3 and it does not work? I can not belive it. I have to write my implementation?

             

            Is the problem (for web BPMN designer): Catching Itermediate Events, Start Events and Throwing Intermediate Events?

            is there any way to work with timers without load session?

             

            amadets