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... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

hi, this could be it as i call ksession.startProcess(processName). is there any way to restart a specific process then as i have problems with finding appropriate API -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/drools-flow-why-after... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

hi, thanks for your prompt reply, OK, i've a custom screen that checks for a task assigned to a specific user. What i'm trying to do now is checking how to restart a process when for instance the server crashes. In order to simulate this i'm killing my process once a human task has been created. After that i'm trying to start the process once again and what i expect is that: - all steps prior to the human task will be skipped - my process will be waiting for a human task to be completed before continuing As you probably correctly pointed out i should be restarting a process rather than starting a new one and trying to use previously stored sessionId. The only problem i see here that i can't find any API that would allow me to do someting like this: processService.restartProcess(processId, sesionId) -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/drools-flow-why-after... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

ok, you're right about the ht node i.e. once i completed the task using reloaded sessionId the process has progressed to the next node. The problem i have though is that i don't think it's enough (unless my understanding is incorrect). Say for a process like below: Start -> WorkItem1(takes 1 hour to complete) -> WorkItem2 (takes 20 min to complete) -> HumanTask -> Stop 1. if my server crashes during WorkItem1 or WorkItem2 there is no way for me to know that after my server has been restarted i should start the process again (ok i could have some other table that would check if a process has been completed) 2. if my server crashes after WorkItem1 but before completing WorkItem2 than i don't really know how i should restart my process. Since WorkItem1 takes 1hour to complete it would be a total overkill for the application to run it once again. That said i'd assume that there should be some way of restarting a process from a specific point i.e. as for point 2, the process should skip WorkItem1 and start to run WorkItem2. Otherwise only HumanTask are the nodes in a process that could restart a process from a specific node -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/drools-flow-why-after... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users