Did you tried Drools 5.1.1? or 5.2? Lots of bugs were fixed since
5.1.0...
Edson
2011/8/24 dcrissman <dac(a)akc.org>
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