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

Persisted timers that expire while JVM is down don't fire upon startup

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: jBPM 5.1
    • Fix Version/s: jBPM 5.4.0.CR1
    • Component/s: Runtime Engine
    • Labels:
      None
    • Environment:

      Local Linux desktop

      Description

      Creating a TimerNodeInstance coupled with JPA persistence that expires while the JVM is down creates a scenario where the timer has expired, and is not fired upon startup.

      For instance: Create a 1 minute timer. Shut down the JVM, wait 2 minutes. Start the JVM back up, re-load the StatefulKnowledgeSession, and the TimerNodeInstance waits in the same state as previous to the deadline, and will not fire.

      Krisv has suggested creating an additional timer unit test to duplicate this scenario.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  swiderski.maciej Maciej Swiderski
                  Reporter:
                  rrpeterson Ryan Peterson
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: