<span style="font-family: Verdana"><p>Thank you for the hint. I've tried to use clearAgenda() but I've following error:</p><p> </p><p><font size="2" color="#ff0000">Exception in thread "main" </font><u><font size="2" color="#000080">java.lang.NullPointerException</font></u></p><font size="2" color="#ff0000"><p align="left">at org.drools.util.LinkedList.remove(<u><font size="2" color="#000080">LinkedList.java:97</font></u><font size="2" color="#ff0000">)<p align="left">at org.drools.common.DefaultAgenda.removeScheduleItem(<u><font size="2" color="#000080">DefaultAgenda.java:150</font></u><font size="2" color="#ff0000">)<p align="left">at org.drools.common.ScheduledAgendaItem.remove(<u><font size="2" color="#000080">ScheduledAgendaItem.java:159</font></u><font size="2" color="#ff0000">)<p align="left">at org.drools.common.DefaultAgenda.clearAgenda(<u><font size="2" color="#000080">DefaultAgenda.java:362</font></u><font size="2" color="#ff0000">)<p align="left">at org.drools.common.AbstractWorkingMemory.clearAgenda(<u><font size="2" color="#000080">AbstractWorkingMemory.java:363</font></u><font size="2" color="#ff0000">)<p>at org.drools.examples.TroubleTicketExample.main(<u><font size="2" color="#000080">TroubleTicketExample.java:58</font></u><font size="2" color="#ff0000">)</font></p></font></p></font></p></font></p></font></p></font></p></font><p><br /> </p><p>Is there anything special to consider when using clearAgenda()?</p><p> </p><p> </p><p> </p><p>----- Edison wrote: </p><p> Technically it is possible and supported to serialize working memories. Although, we did faced problems with large serializations due to a known recursion issue in JDK. There is a JIRA for that, but I don't have the link right now. <br /><br /> Now, if you want to reassert objects without firing rules, maybe what you can do is call WorkingMemory.clearAgenda() after reasserting the objects. Not sure if that will give you the results you expect.<br /><br
/> []s<br /> Edson<br /><br /></p><div><span class="gmail_quote">2007/7/25, Arjun Dhar <<a href="mailto:dhar_ar@yahoo.com">dhar_ar@yahoo.com</a>>:</span> <blockquote style="padding-left: 1ex; margin: 0pt 0pt 0pt 0.8ex; border-left: #cccccc 1px solid" class="gmail_quote"><tom></tom><a target="_blank" href="/xml/deref?link=http%3A%2F%2Fbergstein-soraic.de">bergstein-soraic.de</a>> writes:<br /><br />><br />><br />> I've a use case that is similar to the TroubleTicketExample that is part of<br />the drools examples. <br />> In this examples new tickets are inserted via workingMemory.assertObject<br />(ticket). However, tickets are usually managed and stored in a ticketing system<br />(Remedy, Peregrine, etc). When I stop the drools engine, I assume that the <br />state of the working memory is lost. When I start the engine again, I'd like to<br />load the working memory with the tickets that are stored in the ticketing<br />system, but I don't want to fire all rules, since I'd to avoid that rules are <br />executed again (e.g., rule "Escalate" -> send a e-mail), which have been<br />already executed before the drools engine has<br />> been stopped. Existing tickets in the ticketing system are important facts <br />for the rules!<br />> and therefore the need to be loaded into the morking memory.<br />><br />> <br />> Is there a way to build up the working memory with initial facts?<br />> Can I persist the state of the working memory and load it later again? <br />><br />> <br />> Many thanks in advance,<br />> Tom<br />><br /><br />Hey my two bits,<br /><br />Assuming I dont know much about StatefulSessions holding objects I wanted to<br />check with you, is this safe? I'm not sure over a period of time if your <br />objects would be released with a StatefulSession/WorkingMemory, would recommend<br />you 'soak test' (test over a period of time with consistent l
oad)<br /><br />But here is the possibility:<br />Well the interface WorkinfgMemory -- extends --> Eventmanager which extends <br />Serializable.<br /><br />You could try serializing the object, or query your WorkingMemory for its state<br />and save it to a database. Am assuming you are using StatefulSession so you<br />will have access to WorkingMemory. <br /><br />Conceptually I just think its worng to use a Rule Engine to persist state over<br />a such a long period of time. Any expert opinion?<br /><br />regards,<br />Arjun<br /><br />_______________________________________________<br />rules-users mailing list<br /><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br /><a target="_blank" href="/xml/deref?link=https%3A%2F%2Flists.jboss.org%2Fmailman%2Flistinfo%2Frules-users">https://lists.jboss.org/mailman/listinfo/rules-users </a><br /></blockquote></div><br /><br clear="all" /><br />-- <br /> Edson Tirelli<br /> Software Engineer - JBoss Rules Core Developer<br /> Office: +55 11 3529-6000<br /> Mobile: +55 11 9287-5646<br /> JBoss, a division of Red Hat @ <a target="_blank" href="/xml/deref?link=http%3A%2F%2Fwww.jboss.com">www.jboss.com</a> </span>