Hi O S,
There was an already existing JIRA issue for this, You can find information below.
The problem is caused by two execution in a transation has same ID_. The current solution is using an additional activity to break the transaction. You could add a activity between the timer and state, and set continue="async"
thanks for your reply.
it's not 100% the same, but I guess the root cause must be same or similar
I checked JIRA and it says targeted version 5.1?
Is it me or is this an issue with the most basic jBPM functionality? How could it be scheduled for an idefinite future?
For us it's a pretty much game over for 4.3
where did you find that it is going to be fixed in 5.1? I think it was not scheduled yet.
I agree with you that this is one of the basics that are must to have to be able to use process engine.
Let's vote for the issue and try to include it in 4.4 release.
JIRA says affects versions 4.3 and 4.4 and I assumed that it means is not scheduled to be fixed in 4.4
I thought that the fix version said 5.1, but now I don't see it. Probably made a mistake there
How do I vote? Not registered as a developer and my forum credentials do not let me to login into JIRA
I do beleive that this issue is important to tackle in 4.4
Also I was able to login to JIRA and voted for this as well as linking this discussion in comments