Hi All, I was able to implement some timers and they behave as expected until I enable persistence. Timers work (get triggered) when creating the StatefulKnowledgeSession by kbase.newStatefulKnowledgeSession() but they do NOT work (do not get triggered) when creating the StatefulKnowledgeSession by JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, env); I am calling ksession.fireUntilHalt() from within a new thread and all that. The problem is not getting timers to work, as I have already accomplished this, but the problem is rather getting them to work with persistence enabled. - Has anyone implemented timers while using (having enabled) persistence? - Did you experience any problems such as timers not triggering? - If so, have you found a work around you could share? The timers are being implemented in ruleflow (DRF) and I'm using drools 5.1.0 Any comments are welcome. Thanks, Nick. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Implementing-Timers-W... 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 salaboy, Here is an image of my flow: http://drools-java-rules-engine.46999.n3.nabble.com/file/n923330/SnapShot... Here is the flow definition: <?xml version="1.0" encoding="UTF-8"?> <process xmlns="http://drools.org/drools-5.0/process" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:schemaLocation="http://drools.org/drools-5.0/process drools-processes-5.0.xsd<http://drools.org/drools-5.0/process%0Adrools... " type="RuleFlow" name="simple-embeded-timer-with-persistence" id="simple-embeded-timer-with-persistence" package-name="com.flow" > <header> </header> <nodes> <start id="1" name="Start" x="16" y="16" width="48" height="48" /> <workItem id="2" name="Suspend With Timer" x="96" y="16" width="144" height="48" > <work name="doNothingHandler" > </work> <timers> <timer id="1" delay="500" period="1000" > <action type="expression" dialect="mvel" >System.out.println("**** Timer Triggered ****");</action> </timer> </timers> </workItem> <actionNode id="3" name="Print Out" x="272" y="20" width="80" height="40" > <action type="expression" dialect="mvel" >System.out.println("**** WorkItem Completed!!! Finishing Flow ****");</action> </actionNode> <end id="4" name="End" x="384" y="20" width="80" height="40" /> </nodes> <connections> <connection from="1" to="2" /> <connection from="2" to="3" /> <connection from="3" to="4" /> </connections> </process> Here is the test code: @Test public void shouldStartFlowAndSuspend() { /* * Persistence enabled - Timer does NOT work!!! */ ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, droolsEnvironment); /* * Persistence disabled - Timer DOES work!!! */ //ksession = kbase.newStatefulKnowledgeSession(); sessionId = ksession.getId(); ksession.getWorkItemManager() .registerWorkItemHandler("doNothingHandler", new DoNothingWorkItemHandler()); ksession.startProcess("simple-embeded-timer-with-persistence", null); // start timer thread new Thread() { @Override public void run() { System.out.println("**** Timer thread started ****"); ksession.fireUntilHalt(); } }.start(); // Allow timer to run for 10s try { Thread.sleep(10000); } catch (InterruptedException e) { e.printStackTrace(); } } @Test //NOTE: comment out when not using persistence. public void shouldResumeFlowAndComplete() { ksession = JPAKnowledgeService.loadStatefulKnowledgeSession(sessionId, kbase, null, droolsEnvironment); ksession.getWorkItemManager() .registerWorkItemHandler("doNothingHandler", new DoNothingWorkItemHandler()); ksession.getWorkItemManager().completeWorkItem(1, null); } NOTE: when running WITHOUT persistence the second test method for obvious reasons will fail so it needs to be commented out. Persistence is set up correctly, I've checked the database and everything is being persisted. I can as well resume and complete with no problems BUT the timer is NOT working. Let me know if this is enough and/or if you have any question. Thanks, Nick. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Implementing-Timers-W... 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 Salaboy, Have you had a chance to look into this? Let me know if you have any findings. Thanks, Nick. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Implementing-Timers-W... 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

From my understanding, ksession.getWorkItemManager().completeWorkItem(1,

> commandService.execute(command);

Hi cafebabe, Thanks for your comment. I agree with you that work item ids are database primary keys but in this simple (very simple) case I just decided to harcoded as I know for a fact that the work item id is 1 because that is the only work item and each time I run the test the tables are dropped and recreated. So, there is never more than one row in the workItemInfo table and the only row always has 1 as its id. I could have stored the work item id or a work item object as a variable (like you mentioned) but in this case wouldn't make a difference for the timers. Are timers working for you when you use persistence? I do complete work items by workItem.getId() in all my code (other than this simple example :)). My problem is NOT completing the work item, my problem is triggering timers when persistence is enabled. The timers don't even trigger, thing that should happen before even trying to complete the work item. Thanks, Nick. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Implementing-Timers-W... 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