It seems that the rules that stop firing are dependent on another rule which is responsible for creating drools declared objects with a logicalInsert. Seems to be the only commonality that I can find. Oh, and I am using a stateless session. Example: declare MyClass end rule "Create Instance" when //whatever then logicalInsert(new MyClass()); end rule "Dependent" when MyClass( //whatever ) then //do something end -- View this message in context: http://drools.46999.n3.nabble.com/Rules-stop-firing-when-white-space-is-c... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Incremental change set processing might create the effect you describe. Declared types are always replaced; rules only if they differ. It sure would be nice if the effects of knowledge base updates were described in a way that leaves no room for guesswork. "Gimme hope, Jo'anna..." -W On 23 August 2011 21:35, dcrissman <dac(a)akc.org&gt; wrote: > It seems that the rules that stop firing are dependent on another rule > which > is responsible for creating drools declared objects with a logicalInsert. > Seems to be the only commonality that I can find. > > Oh, and I am using a stateless session. > > Example: > > declare MyClass > end > > rule "Create Instance" > when > //whatever > then > logicalInsert(new MyClass()); > end > > rule "Dependent" > when > MyClass( > //whatever > ) > then > //do something > end > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Rules-stop-firing-when-white-space-is-c... > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Esteban wrote: > > What are the steps you are following? Something like this?: > > The agent creates the kbase > Get kbase from kagent > Create a stateless ksession > insert some facts > fire all rules > check result > modify drl > wait until kagent rebuilds the kbase > get the new kbase from kagent > Create a stateless ksession > insert some facts > fire all rules > check result > > Also, which version of Drools are you using? > The steps you outline are correct. That modification can be white space or an actual logic change; but does not need to be localized in the rule that stops working. Drools Version: 5.1.0 Wolfgang wrote: > > Incremental change set processing might create the effect you describe. > Declared types are always replaced; rules only if they differ. > Esteban wrote: > > He doesn't seem to be using KAgent in incremental mode. So, each time a > change is detected, a new KBase is created. All sessions previously > created will continue using the old kbase. > He is using Stateless ksessions. > As Esteban inferred, incremental mode is not being used. A new session is created with each run. -- View this message in context: http://drools.46999.n3.nabble.com/Rules-stop-firing-when-white-space-is-c... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Esteban wrote: > > What are the steps you are following? Something like this?: > > The agent creates the kbase > Get kbase from kagent > Create a stateless ksession > insert some facts > fire all rules > check result > modify drl > wait until kagent rebuilds the kbase > get the new kbase from kagent > Create a stateless ksession > insert some facts > fire all rules > check result > > Also, which version of Drools are you using? > The steps you outline are correct.

Wolfgang Laun-2 wrote: > > On 24 August 2011 15:34, dcrissman &amp;lt;dac(a)akc.org&amp;gt; wrote: > >> >> Esteban wrote: >> > >> > What are the steps you are following? Something like this?: >> > >> > The agent creates the kbase >> > Get kbase from kagent >> > Create a stateless ksession >> > insert some facts >> > fire all rules >> > check result >> > modify drl >> > wait until kagent rebuilds the kbase >> > get the new kbase from kagent >> > Create a stateless ksession >> > insert some facts >> > fire all rules >> > check result >> > >> > Also, which version of Drools are you using? >> > >> >> The steps you outline are correct. >> > > You cannot "insert some facts" and "fire all rules" on a stateless > knowledge > session. So what is the sequence of API calls? Configurations? > -W > We have a web application running on Tomcat. The user can initiate an action that fires a series of stateless drules rules. If I fire up the application on tomcat and execute the action in the portal that runs the drools rules it works. If I change the drl file while tomcat is still running, wait for the altered rules to be loaded, then execute the action again. Some rules will not fire the second time that fired the first time. -- View this message in context: http://drools.46999.n3.nabble.com/Rules-stop-firing-when-white-space-is-c... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Wolfgang Laun-2 wrote: > > The only thing you can do with a Stateless Knowledge Session is to call > its > execute method, overloaded to take a single object or a collection of > objects to be inserted > or a command to be executed. A command may not do much more than execute > with insert(s): get/setGlobal is also possible. What commands are applied > to > the session? > > What happens if you reexecute the action without a change in the DRL? > > -W > Some globals are being set, but most objects are being inserted. The rules produce the expected outcome even after multiple loads, until a change is made to the drl file. -- View this message in context: http://drools.46999.n3.nabble.com/Rules-stop-firing-when-white-space-is-c... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users