[
https://jira.jboss.org/jira/browse/JBPM-1170?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1170:
-----------------------------------
a note should be added in the docs that each timer must have a unique name.
"
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.
"
in the docs, a note should be added to describe this limitation.
Multiple Timers with same name on Node end prematurely
------------------------------------------------------
Key: JBPM-1170
URL:
https://jira.jboss.org/jira/browse/JBPM-1170
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 3.2.2
Environment: Jbpm 3.2.2, Tomcat 5.028, MySQL 5.0
Reporter: David Roberts
Fix For: jBPM 3.3.x
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira