]
Alejandro Guizar resolved JBPM-1170.
------------------------------------
Labels: jbpm3 node task timer (was: )
Assignee: Alejandro Guizar
Fix Version/s: (was: jBPM 3.2.x)
Resolution: Won't Fix
Multiple task instances of the same task is arguably an "edgy" use case. Fixing
the problem would require timer name mangling, which is nontrivial to implement and
unjustified given the low demand for this issue.
Multiple Timers with same name on Node end prematurely
------------------------------------------------------
Key: JBPM-1170
URL:
https://jira.jboss.org/browse/JBPM-1170
Project: jBPM
Issue Type: Bug
Components: Runtime Engine
Affects Versions: jBPM 3.2.2
Environment: Jbpm 3.2.2, Tomcat 5.028, MySQL 5.0
Reporter: David Roberts
Assignee: Alejandro Guizar
Labels: jbpm3, timer, task, node
When you have multiple Tasks on a Node, and each task has a Timer called, for example,
"Reminder". Lets say each timer is set to repeat every 24 hours. If you complete
one of the Tasks on the node, the Timer called "Reminder" on that task instance
ends, but so does every other timer for all other tasks on that node with the name
"Reminder". Surely this should not happen?
You could avoid this by naming each Timer differenty, example "Reminder 1",
"Reminder 2". But the problem may still happen if you have multiple task
instances of the SAME task. Then the name of the Reminders will still be the same, so they
will all end when completing one of the task instances.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: