October 2011 - rules-users - Jboss List Archives

[drools 5.3.0.Final] Predicate ... must be a Boolean expression

by kennywest

I did a quick search in the mailing list, but couldn't find a related issue. The following rule worked fine in 5.3.0.CR1 (and earlier) ... when $party : ImmutableParty(addresses == null || addresses.size() == 0) then ... ImmutableParty has a getter for addresses and addresses is a collection. When upgrading to 5.3.0.Final, I get this error: Caused by: java.lang.RuntimeException: Predicate 'addresses == null || addresses.size() == 0' must be a Boolean expression [Line: 17, Column: 32] : [Rule name='party - address - at least one'] This is with mvel 2.1 beta 6. -- View this message in context: http://drools.46999.n3.nabble.com/drools-5-3-0-Final-Predicate-must-be-a-... Sent from the Drools: User forum mailing list archive at Nabble.com.

14 years, 1 month

2
2
0 / 0

Drools 5.3.0.Final with jBPM

by Melton, Michael P CTR SPAWARSYSCEN-ATLANTIC, 01200

Is there a recommended version of jBPM to use in conjunction with Drools 5.3.0.Final? We are currently using jBPM 5.1.0.Final alongside Drools 5.2.0.Final, but I see in Nexus that jBPM has 5.1.1Final and 5.1.2.Final releases and I'd like to only upgrade one time. Thank you.

14 years, 1 month

2
1
0 / 0

Fwd: Questions

by Michael Anstis

Anybody? ---------- Forwarded message ---------- From: Damien Renier All, I’m trying to prepare some answers to questions of a customer The client wish to execute some rules on dates which are not today. The rule is: 1. | rule "TooYoung" 2. | date-expires "26-MAR-2013" 3. | date-effective "19-MAR-2010" 4. | dialect "mvel" 5. | when 6. | Driver( age < "16" ) 7. | then 8. | Rejection fact0 = new Rejection(); 9. | fact0.setReason( "TooYoung" ); 10. | insert(fact0 ); 11. | System.out.println("TooYoung"); 12. | end First test with execution date set to today in Guvnor/test-scenario Rule is executed - OK Second test with execution date set to tomorrow Rule is executed – OK Now one change the rule’s attributes and execution date Execution date = 20-MAR-2011 date-effective = 19-MAR-2010 date-expires = 26-MAR-2011 no execution Execution date = 20-MAR-2012 date-effective = 19-MAR-2012 date-expires = 26-MAR-2013 no execution So my guess is the execution date is ignored. I tried to use the AgendaFilter unsuccessfully. ksession.fireAllRules(new AgendaFilter() { public boolean accept(Activation a) { System.out.println("-- " + a.getRule().getName()); return true; } }); But this code do not work for the specific rule above, others with no date attributes are going through and the sysout do its job. My question is: How can I tell the engine which rule to execute based on the execution date? Maybe this behaviour is only in Guvnor. Is it possible to set an execution date to the engine which is not today and how to do it? Thank you Damien

14 years, 1 month

1
0
0 / 0

[drools planner 5.3.0 Final] cached planning values

by guyver

I get the following exception when i try to solve and don't know if i didn't set something properly on my side or if there is a bug in the planner. After debugging, seems like cachedPlanningValues in PlanningValueCreator is being created as an empty collection and when PlanningValueWalker gets cachedPlanningValues's iterator and tries to iterate through it then it gets a NoSuchElementException. I am a little confused as to when the extractPlanningValues method is called in PlanningValueSelector to get a collection of planned values a null is begin passed in instead of a planning entity which is responsible for the empty cachedPlanningValues collection. Any help on this issue will be much appreciated. java.util.NoSuchElementException at java.util.AbstractList$SimpleListIterator.next(AbstractList.java:61) at org.drools.planner.core.heuristic.selector.variable.PlanningValueWalker.initWalk(PlanningValueWalker.java:90) at org.drools.planner.core.heuristic.selector.variable.PlanningVariableWalker.initWalk(PlanningVariableWalker.java:104) at org.drools.planner.core.constructionheuristic.greedyFit.decider.DefaultGreedyDecider.decideNextStep(DefaultGreedyDecider.java:58) at org.drools.planner.core.constructionheuristic.greedyFit.DefaultGreedyFitSolverPhase.solve(DefaultGreedyFitSolverPhase.java:62) at org.drools.planner.core.solver.DefaultSolver.runSolverPhases(DefaultSolver.java:166) at org.drools.planner.core.solver.DefaultSolver.solve(DefaultSolver.java:138) -- View this message in context: http://drools.46999.n3.nabble.com/drools-planner-5-3-0-Final-cached-plann... Sent from the Drools: User forum mailing list archive at Nabble.com.

14 years, 1 month

2
2
0 / 0

Decision Table with more than 9 parameters

by marta

Hi, I've a problem with Drools 5.1.1. I'm using a decision table to write my rules and I need to use more than 9 parameters in the same action, but something doesn't work. In fact the $10 parameter is interpreted by Drools as the first parameter ($1) with 0 appended on queue. Does exist a different way to write the tenth (or greater) parameter? Thanks. -- View this message in context: http://drools.46999.n3.nabble.com/Decision-Table-with-more-than-9-paramet... Sent from the Drools: User forum mailing list archive at Nabble.com.

14 years, 1 month

2
1
0 / 0

[planner][5.3.0.Final] Benchmark

by Guilherme Kunigami

I'm trying to upgrade from drools 5.2.0 to 5.3.0 and having some difficulties with the planner benchmark. I'd like to make a set of move factories common to all local search solvers, by adding them to inheritedSolverBenchmark block. But it seems that the localSearch environment always requires a selector, so I can't specify the localSearch environment for the solverBenchmark's without providing a selector. Here's a piece of code that gives runtime error: http://paste.ubuntu.com/718806/ The error is: Exception in thread "main" java.lang.IllegalArgumentException: A selector requires configuration, for example a moveFactoryClass. --- Note --- If I understood correcly, the following configuration from examination examples: examinationStepLimitSolverBenchmarkConfig.xml contains a bug, because it specifies a maximum step count for a general solver <termination> <maximumStepCount>70</maximumStepCount> </termination> This gave the following exception: Exception in thread "main" java.lang.UnsupportedOperationException: StepCountTermination can only be used for phase termination. Thanks,

14 years, 1 month

2
1
0 / 0

Looking for a Drools lecturer

by Laurence Vignollet

Hello, We have introduced a "rule-engine" course in a 5th year of Computer Science Study in University of Savoie, France. We would like to give some hours on a Drools initiation, including practise, to the 20 students attending this course. If somebody could be interested, please contact me by email. Thanks in advance, all the best, Laurence Vignollet -- Université de Savoie Campus Scientifique 73370 Le Bourget-du-Lac Tel : +33 (0)479 758 847 Fax : +33 (0)479 758 690

14 years, 1 month

3
2
0 / 0

Advice on varying rule behavior based on object tested?

by zstlaw

Each item I am testing MAY have overridden the default thresholds or disable the rule entirely. I would prefer to have this data related to the item I am testing rather than have each rule manage customized behavior for thousands of different types of objects. The object could have a map of rule thresholds it overrides, but for simplicity I assume there is a method to return the current threshold for the current object. is there a better way to perform this kind of logic? Example of my current code: declare TestedEntity temp : Double end declare AlertThreshold maxAllowed : Double end rule "Check temperature" when $entity : TestedEntity( ) // would prefer to use drools.getRule().getName() on next line AlertThreshold($entity.temp > maxAllowed) from $entity.getAlertThresholdForRule("Check temperature") then // raise alert end I dislike hard-coding the rule name as it leads to copy paste errors. I can't insert thresholds easily unless I define different ones for each rule and I want to be able to fall back to defaults easily. This is a type of problem I have come up against several times now so I feel like others must have dealt with it before. The idea of writing copies of rules tailored to each Entity appeals less than a generalized way of doing this. By doing this I want to contain complexity. Dozens of slightly different implementations of the same rule would be much harder to test and support. I am dealing with hundreds of thousands of facts today and will need to scale to millions before I can deploy fully. But with that large number I need to have ways to manage exceptions to the general case just to keep complexity manageable. Thanks, Zack -- View this message in context: http://drools.46999.n3.nabble.com/Advice-on-varying-rule-behavior-based-o... Sent from the Drools: User forum mailing list archive at Nabble.com.

14 years, 1 month

2
1
0 / 0

WorkingMemoryLogger + statelessSessions = memory leak?

by Swindells, Thomas

Hi everyone, I believe that there is a memory leak when using WorkingMemoryLoggers with statelessSessions. This was raised against 5.1.1 but I think it will still exist in the latest as well. Our code basically has the following pattern: KnowledgeBase kb ==; while(nextEvent()) { StatelessKnowledgeSession session = kb.newStatelessKnowledgeSession(); auditor = new WorkingMemoryInMemoryLogger(session); session.execute(getEvent()); dumpAuditLog(auditor); session = null; //no dispose it's stateless } We were getting Out of Memory Exception on site and the stack dump showed a high number of MemoryLoggers on the heap. Having a look at the code I think the problem is in the WorkingMemoryLogger constructor: } else if (session instanceof StatelessKnowledgeSessionImpl) { ((StatelessKnowledgeSessionImpl) session).workingMemoryEventSupport.addEventListener( this ); ((StatelessKnowledgeSessionImpl) session).agendaEventSupport.addEventListener( this ); ((StatelessKnowledgeSessionImpl) session).ruleFlowEventSupport.addEventListener( this ); ((StatelessKnowledgeSessionImpl) session).getRuleBase().addEventListener( this ); } The last statement gets the knowledge base and attaches the event listener to it. As far as I can see there is no way to dispose of the WorkingMemoryLogger and you don't dispose stateless sessions (and it doesn't know about the listener anyway). This means that even after the session is gone the rule base still has a reference to the logger. The work around is to make the logger a singleton and clear it in each loop rather than creating a new one each time, however this obviously doesn't scale to multiple threads. Have I missed some fundamental in the api or should I raise a Jira for this? Thomas ________________________________ ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster(a)nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************

14 years, 2 months

1
1
0 / 0

Rule, import with wildcards and variable / patternBinding

by Per Sterner

Hello, Yesterday I wanted to upgrade my drools version to 5.3 (from 5.1). I got the exception "java.lang.NoClassDefFoundError: de/pelle7/testpackage/event/myEvent (wrong name: de/pelle7/testpackage/event/MyEvent)" while adding my resources. I removed the import wildcards and the error disappeard. Finally I found the problem: I used the patternBinding 'myEvent' and there is a class called 'MyEvent' and I used an wildcard import where the class 'MyEvent' is located. Example code: " package de.pelle7.testrules.impl.drools import de.pelle7.testpackage.event.* rule "Test rule 1" dialect "java" salience 50 when myEvent : MyEvent( ) myEvent2 : MyEvent( data == myEvent.data ) <-- here the Exception is thrown then System.err.println("Output"); end " My solution is that I replaced all my pattern bindings with the suffix '$' which is more convenient. Perhaps it would be nice to produce an rule-compilation error. with a line notice. Regard, Per Sterner

14 years, 2 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

rules-users October 2011