Timer Start Event ignores Time Cycle value if iteration count not present

Description

Timer Start Events do not work correctly when the Time Cycle value is set without an iteration count (i.e. R/PT1M). The issue is repeatable. The manifestation of the problem is that, once deployed, the workflow correctly waits for the specified interval (in the example given, 1 minute) and starts the workflow. It then waits for a 2nd correct interval, and then starts the workflow as often as it can, on the order of .1 sec per execution. The timer start event works correctly if an interval count (i. e. R10/PT1M) is used.

The enclosed unit passes, but duplicates the problem seen in the attached log file.

Environment

Ubuntu Linux 15.04, Java 1.7, Tomcat 8.0.15,

Assignee

Tijs Rademakers

Reporter

MarkV

Labels

None

Components

Fix versions

Affects versions

Priority

High
Configure