hi, i've a simple drools flow process with one workItem (its execute method simply prints some text) and one human task. I'm using drools-persistence-jpa to save my process status and load it when process/server crashes. What i've noticed is that: 1. after starting process my processinfo table gets updated with a new process status (P1) 2. my workItem (W1) runs correctly and prints a text 3. a human task gets created ----- when i stop my server at this point and restart my server executing below steps 1. load the session using JPAKnowledgeService.loadStatefulKnowledgeSession(myPreviousSessionId,....) 2. start the process
At this point previously completed workItem (W1) gets executed once again and the same human task gets created !! I thought that perhaps the issue is with my transactionManager not committing steps but since i'm using local transaction (commit happens after any process step) its very unlikely. Is it a bug that the same workItem gets executed or is it intentional and it's up to the developer to check somewhere else whether specific step has been already finished or not..? -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/drools-flow-why-after-reloading-some-process-previously-completed-workItems-gets-executed-once-again-tp2784850p2784850.html Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
