I already used a global limit of rule's firing with success to prevent these
kind of problems (with a big number, eventually calculated from rules as
Wolfgang said).
This works, at least to detect infinite loops, because usually, when this
happend, the number of firing increases very fast so the
On 15/05/2012, mike wrote:
> that's nice ... n' a bit clever ... it could work ... I mean, i could
> automatically append that to all sessions given that i control compiling
> the drls.
>
> Is there any setting or something that detects infinite loops? Like it
> would abort if if drools runs into
that's nice ... n' a bit clever ... it could work ... I mean, i could
automatically append that to all sessions given that i control compiling
the drls.
Is there any setting or something that detects infinite loops? Like it
would abort if if drools runs into an infinite loop?
I guess I could do s
A very low salience rule depending on nothing and calling halt will stop
the run:
rule Exit
salience -9
when
then
drools.halt();
end
-W
On 15 May 2012 21:46, mike wrote:
> Well I got this wrong sorry. Yes I can stop a session if I start it with
> fireUntilHalt() but it never stops.
Well I got this wrong sorry. Yes I can stop a session if I start it with
fireUntilHalt() but it never stops. I need it to finish by itself too.
Thank you
Mike
On Tue, May 15, 2012 at 11:06 AM, mike wrote:
> wow that worked like a charm!!! thank you very much Wolfgang, I owe u a
> beer or some
wow that worked like a charm!!! thank you very much Wolfgang, I owe u a
beer or something :)
Cheers
Mike
On Tue, May 15, 2012 at 11:01 AM, mike wrote:
> Awesome I'll try that :)
>
> We got business ppl writing rules ... Those rules are going on infinite
> loops quite often ... Frankly I am no
Awesome I'll try that :)
We got business ppl writing rules ... Those rules are going on infinite
loops quite often ... Frankly I am not excited about killing the session,
for me it's just a business request that I am trying to implement
Thank you very much Wolfgang
Cheers
Mike
On Tue, May 15,
You are confusing jBPM processes and Java threads.
You can interrupt the thread SessionThread, but that's not reliable
(if IE is handled, for instance),
Best would be to call fireUntilHalt() and call the session's halt method.
But why would you want to do this sort of weird thing?
-W
On 15/05
Hi there,
Is there any way to kill a running session?
I've been trying with StatefulKnowledgeSession.abortProcessInstance but i
can't get it working.
For instance .. I got this drl
rule "infinite loop"
when x : Integer()
then
System.out.println(x);
Thread.sleep(100);
