Hi,
for sure this is not a known issue, so can you please open a jira and attach
your reproducer there?
I'll investigate this problem asap.
Thanks a lot,
Mario
--
View this message in context:
Ciao Mario, thanks for your early feedback
Raised as: https://issues.jboss.org/browse/DROOLS-516
Looking forward looking to comments on this JIRA, then.
Ciao
Matteo
On Thu, Jun 5, 2014 at 1:42 PM, Mario Fusco mario.fu...@gmail.com wrote:
Hi,
for sure this is not a known issue, so can you
Running Drools for event processing can be done in several ways, but some
of them will not produce the expected results.
One good way is to use a real time clock, call fireUntilHalt() in one thread and
insert facts (as they arrive) via another thread.
Another one, good for tests, is to use a
Hi,
We are using Drools for a heavy process and we notice some slowness during
the first calls to kbases (containing about 1500 rules each) using
StatefulKnowledgeSession.
Even if the kbase is loaded, we need to make some fictive calls (fire
the rules with some facts) until it begins to respond
On 5 Jun 2014, at 16:48, Gael gael.weil-jour...@prestataire.april.com wrote:
Hi,
We are using Drools for a heavy process and we notice some slowness during
the first calls to kbases (containing about 1500 rules each) using
StatefulKnowledgeSession.
Even if the kbase is loaded, we need to
Google: JIT Java
-W
On 05/06/2014, Gael gael.weil-jour...@prestataire.april.com wrote:
Hi,
We are using Drools for a heavy process and we notice some slowness during
the first calls to kbases (containing about 1500 rules each) using
StatefulKnowledgeSession.
Even if the kbase is loaded, we
I've created a repo on github you can clone to reproduce the issue. It is
located at:
https://github.com/caskater4/kie-wb-error
I thought I had isolated the problem down to the project having specified
drools-core as a dependency but when I attempted to create a repo with only
that it didn't
Hi Mario,
Although I fixed the no-validation problem by uninstall/reinstall the drools
runtime as my last message said, it is not a stable solution. Sometimes it
stops to do validation again so I have to repeat the steps.
So I look into the code, and find out oldLoader is an instance of
