Will somebody help me? It is very important for me!
Were you able to run this piece of code with the jbpm-jpdl-suite? i.e on JBoss AS 4.0.x?
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.
To solve this problem, I was forced to remove "transition" attribute.
In principle, it is logically :-))
But, is it correct behaviour of jBpm?
no, it is not logical
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:
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
ahhh.. yes... good observation....
IMO The code should ignore the repeat if there is a transition.. agreed? Please file a jira issue for this.