Thanks for your reply.
I tried around and found out that the main problem seemed to be the multithreaded setup combined with fireUntilHalt().
When I switched to single threaded and using fireAllRules() every 1000 events everything works fine. No race conditions. (And no freezing when
We have a program that validates large amount of data. When changing this
program to use drools 6.0.1 instead of 5.5.0, this GC overhead limit
exceeded problem occurred.
Program reads one object to memory, then validate it and then retract it.
This is repeated thousands of times.
java version
Dear OptaPlanner users,
I am working for a small company located in Munich and have a software
problem, which I would like to solve with OptaPlnner.
In our case, we have multiple technicians which are starting their work each
day from different locations (e.g. their homes).
Each technician has
On 22-01-14 14:56, milenko wrote:
Dear OptaPlanner users,
I am working for a small company located in Munich and have a software
problem, which I would like to solve with OptaPlnner.
In our case, we have multiple technicians which are starting their work each
day from different locations
We have two set of rules. Some of them are static. Some of them changes
frequently. We need to find a way to keep the pre-compiled version of those
rules into filesystem and import them into knowledge base at run time. So
that over all performance to prepare the knowledge base will minimize.
I
That is upsetting to hear that you need the paid edition of IntelliJ for any
Drools support. I can't justify shelling out the money for IDE for a single
(albeit very attractive) feature.
The weird thing is that I could really live without any of the code completion
or deep rules analysis. My
Why store serialised kiebases? Is it really that expensive to consume a kjar?
As long as you build with drools maven plugin, it should have a lot of aspects
pre-ompiled now.
Our incremental “diff” will take care of static and dynamic aspects, if you
always build and deploy new jars, using the
I'd say it's a bug... maybe indexing is involved?
Replacing ruleA's LHS with
$p: Parent( $a2 : attribute2 != null)
?getChildWithName($a2 , n1, $child;)
makes it work as expected. I will investigate further.
Davide
On 01/22/2014 02:22 PM, Esteban Aliverti wrote:
Hi guys,
I was writing
Indeed, the use case can be simplified further:
package org.drools.test.bc;
declare Parent
attribute2 : String
end
declare Child
parentId : String
end
query getChildWithName( String $parentId, Child $child )
$child:= Child( parentId == $parentId )
end
rule Insert Children
when
Good catch Davide. I can confirm that not using nested accessors the query
works as expected.
Regards,
Esteban Aliverti
- Blog @ http://ilesteban.wordpress.com
On Wed, Jan 22, 2014 at 6:57 PM, Davide Sottara dso...@gmail.com wrote:
Indeed, the use
10 matches
Mail list logo
