Obviously, it should be for (int i=0; i facts.length;i++), right?
2011/9/23 Manohar Kokkula manohar.kokk...@tcs.com
Hi,
I am trying to execute Banking Tutorial Example given in Drools expert(*
Below is my idea.
The rule check that there is
1) no event between E1 and E2 and
2) no event after E2
which induce that E1 and E2 are the last 2 event. I think it should work but
I didn't test it.
rule Props
when
$E1 : MyEvent(prop1 == MyProp) from entry-point MyStream
$E2 :
Are the test cases failed because of
java.lang.NullPointerException
at
org.drools.command.runtime.BatchExecutionCommand.execute(BatchExecutionCommand.java:142)
at
org.drools.command.runtime.BatchExecutionCommand.execute(BatchExecutionCommand.java:1)
at
and distribution of
your knowledge session across the grid and also do that transparently for
your application :)
Greetings.
On Mon, Aug 16, 2010 at 2:20 AM, Tan Hui Onn hui...@gmail.com wrote:
Some additional note to my question. The intended clustering need not
to support session failover
Hi Nick and Kris,
I tested with latest codes from trunk, both Nick's test (Timer with
ksession.fireUntilHalt()) and
PersistentStatefulSessionTest.testPersistenceTimer() are working now
(i.e Timer Triggered was printed).
Thanks and best regards,
Hui Onn
On Thu, Jul 22, 2010 at 6:58 AM, nanic23
I just found out that this is a (fixed) known issue:
https://jira.jboss.org/browse/JBRULES-2552
Deadlock when using fireUntilHalt on SingleSessionCommandService
On Tue, Jul 13, 2010 at 7:49 PM, Tan Hui Onn hui...@gmail.com wrote:
Hi Nick,
You are absolutely right that the timer
Hi Nick,
You are absolutely right that the timer is not triggered in
CommandBasedStatefulKnowledgeSession (which is used for JPA
persistence). I have spent some time to troubleshoot it. There is some
finding regarding to this problem. Maybe other experts are willing to
solve it.
In
