-
1. !!!
slogger Jun 29, 2007 2:07 AM (in response to slogger)Will somebody help me? It is very important for me!
-
2. Re: Malicious timer :)
koen.aers Jun 29, 2007 2:58 AM (in response to slogger)Were you able to run this piece of code with the jbpm-jpdl-suite? i.e on JBoss AS 4.0.x?
Regards,
Koen -
3. FFF
slogger Jun 29, 2007 3:19 AM (in response to slogger)Yes I was. I said above about my soft environment )
By the way, I replace jbpm-console.war v3.2.1 with v3.2 and it began to work normally, except jbpm Timer. -
4. Re: Malicious timer :)
slogger Jun 29, 2007 6:55 AM (in response to slogger)To solve this problem, I was forced to remove "transition" attribute.
In principle, it is logically :-))
But, is it correct behaviour of jBpm? -
5. Re: Malicious timer :)
kukeltje Jun 29, 2007 8:20 AM (in response to slogger)no, it is not logical
-
6. Re: Malicious timer :)
syngolis Jun 29, 2007 9:26 AM (in response to slogger)While working on other timer-problems I tested this case as well.
If you set an transition on a timer, this transition will be taken if it reaches the
duedate and no further repetitions are possible cause the timer is deleted from db. So far so good...
But if you set the repeat option as well, the engine tries to execute the timer once more:
1. DueDate:[STDOUT] Message!
After that execution goes on.
2. But there is another repeat...[ExecuteTimerCommand] execution of timer 25 was skipped cause the timer was deleted from the database
-
7. Re: Malicious timer :)
kukeltje Jun 29, 2007 10:25 AM (in response to slogger)ahhh.. yes... good observation....
IMO The code should ignore the repeat if there is a transition.. agreed? Please file a jira issue for this. -
8. Re: Malicious timer :)
syngolis Jun 29, 2007 11:01 AM (in response to slogger)jira created http://jira.jboss.com/jira/browse/JBPM-1006