I mean to say is that, control does not come back to
workingMemory.fireUntillHalt(). It just hangs in the rule file itself. Does
not do anything at all.
What is the use of that.
If I write like halt in the rule then it should stop the rule firing and
control should be sent back to
Is the consequence of the rule where you call
drools.halt()
really executed?
-W
On 21/08/2012, Rana ven12...@yahoo.com wrote:
I mean to say is that, control does not come back to
workingMemory.fireUntillHalt(). It just hangs in the rule file itself. Does
not do anything at all.
What is
Ok, it is working now. I don't know what was the problem. I guess the rules
were not right before.
One question, my rules have the same facts, and this is why it is activating
all the satisfied rules before firing. is there anyway to stop this.
I mean think about it. If I have million rules with
On 21/08/2012, Rana ven12...@yahoo.com wrote:
One question, my rules have the same facts, and this is why it is
activating
all the satisfied rules before firing. is there anyway to stop this.
How do you determine that there are many satisfied rules? And, if
they are on the agenda after
Here is the example
rule AndroGel Provider State
no-loop true
salience 95
agenda-group AndroGel
when
eval( droolsRequest.address.stateCode == MA )
then
logging();
drools.halt();
end
the other rule is very
Instead of grouping your rules using agenda-group maybe you could partition
your kbase to only have the rules for a particular Product (?)
Best Regards,
Esteban Aliverti
- Blog @ http://ilesteban.wordpress.com
On Tue, Aug 21, 2012 at 5:00 PM, Rana
I am actually using ChangeSet, because we did not wanted the rule files to
loaded many times, rather load at once and use scanner to look for any
changes.
--
View this message in context:
http://drools.46999.n3.nabble.com/fireUntilHalt-is-halt-forever-tp4019146p4019317.html
Sent from the
You can still have different change-sets pointing to different resources
(you can share these resources too) for different kbases.
Best Regards,
Esteban Aliverti
- Blog @ http://ilesteban.wordpress.com
On Tue, Aug 21, 2012 at 5:21 PM, Rana
You are not writing rules - you are using rules to disguise the fact
that you are using if statements to process your data.
What is droolsRequest and how is it declared? If this were a real rule,
it would be
when
DroolsRequest( address.stateCode == MA )
then
...
no-loop is nonsense in a
I am using Working Memory instead of kSession. And it is not working at all.
It just hangs after drools.halt();
Please let me know about it.
Thanks.
--
View this message in context:
http://drools.46999.n3.nabble.com/fireUntilHalt-is-halt-forever-tp4019146p4019290.html
Sent from the Drools:
On 20/08/2012, Rana ven12...@yahoo.com wrote:
I am using Working Memory instead of kSession. And it is not working at
all.
It just hangs after drools.halt();
Well, halt() means do not continue. What on earth do you expect?
-W
Please let me know about it.
Thanks.
--
View this message
Hi my rule file is halt for ever. Can anybody tell me why. I debugged and saw
that it is going into this method in DefaultAgenda.class
public void fireUntilHalt(final AgendaFilter agendaFilter) {
synchronized ( this.halt ) {
if( !this.halt.get() ) this.halt.wait(); //it
Hi,
yes if you use : drools.halt();
that will stop the session.
What exactly do you want to achieve with that?
Cheers
On Wed, Aug 15, 2012 at 5:49 PM, Rana ven12...@yahoo.com wrote:
Hi my rule file is halt for ever. Can anybody tell me why. I debugged and
saw
that it is going into this method
Thanks for your reply.
Once all the rules of that file is good, then it should retrieve the
resources in the rule file but not the session. and then may be fire other
rule file.
Thanks.
--
View this message in context:
I guess you call kSession.fireUntilHalt(). This call should return
after drools.halt() is called from one of the rules. Java code
following this call should do whatever needs to be done. (I don't know
what you mean by retrieve the resources)
-W
On 15/08/2012, Rana ven12...@yahoo.com
Nope it is not working like that.
I removed it. Using fireAll
Thanks.
--
View this message in context:
http://drools.46999.n3.nabble.com/fireUntilHalt-is-halt-forever-tp4019146p4019153.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
Thanks for your comment, Edson.
I have been using 5.3.0.Final. I could easily move to 5.4.0.Final but I
don't see any of the 5.4.x branches at Maven Central. Is there another
repository that has more up to date releases?
Craig
--
View this message in context:
I have a fairly complicated drools program and I want to introduce temporal
reasoning to it. I spent a bit of time writing some proof-of-concept
programs to get the feel of fusion and then tried to slowly introduce things
into my original drools program. When I changed my program from using
Which Drools version are you using?
There are no secrets, but you have to be aware that in this mode rules
will fire right away if they can. Also, if you are using 5.4.0.Final,
please read another e-mail I sent to the list today, as there was a
concurrency bug that was fixed in the 5.4.x
Observed this on Drools 5.1.1 final when fireUntilHalt() is used.
The issue is reported as 'Resolved' in post:
https://issues.jboss.org/browse/JBRULES-2756; in Drools 5.2.0 M1.
So tried the same on Drools 5.2.0 final 5.2.0 M1. Also when I try to make
the recommended code changes in drools-core
access into the working
memory.
Thomas
-Original Message-
From: rules-users-boun...@lists.jboss.org [mailto:rules-users-
boun...@lists.jboss.org] On Behalf Of Edson Tirelli
Sent: 06 October 2010 01:28
To: Rules Users List
Subject: Re: [rules-users] fireUntilHalt and timing of rule
: Tue, October 5, 2010 5:27:58 PM
Subject: Re: [rules-users] fireUntilHalt and timing of rule activations
Norman,
What you say makes sense, but it is not implemented. It is
something I think would be good to have. May I suggest you open a JIRA
for it so we track it?
Meanwhile, the workaround
--
*From:* Wolfgang Laun wolfgang.l...@gmail.com
*To:* Rules Users List rules-users@lists.jboss.org
*Sent:* Sun, October 3, 2010 10:51:08 PM
*Subject:* Re: [rules-users] fireUntilHalt and timing of rule activations
2010/10/4 Greg Barton greg_bar...@yahoo.com
If you don't have some way
: Greg Barton greg_bar...@yahoo.com
To: Rules Users List rules-users@lists.jboss.org
Cc: Rules Users List rules-users@lists.jboss.org
Sent: Tue, October 5, 2010 5:03:33 PM
Subject: Re: [rules-users] fireUntilHalt and timing of rule activations
The entire purpose of fireUntilHalt is to do exactly
To: Rules Users List rules-users@lists.jboss.org
Sent: Tue, October 5, 2010 11:34:53 PM
Subject: Re: [rules-users] fireUntilHalt and timing of rule activations
Norman,
if you create the Jira, please include my suggestion to make this call accept a
collection of facts without any intervening Engine
: Wolfgang Laun wolfgang.l...@gmail.com
To: Rules Users List rules-users@lists.jboss.org
Sent: Sun, October 3, 2010 10:51:08 PM
Subject: Re: [rules-users] fireUntilHalt and timing of rule activations
2010/10/4 Greg Barton greg_bar...@yahoo.com
If you don't have some way of associating
of
that change in working memory are completed.
Thoughts?
Norman
From: Wolfgang Laun wolfgang.l...@gmail.com
To: Rules Users List rules-users@lists.jboss.org
Sent: Sun, October 3, 2010 10:51:08 PM
Subject: Re: [rules-users] fireUntilHalt and timing of rule
.
Thoughts?
Norman
From: Wolfgang Laun wolfgang.l...@gmail.com
To: Rules Users List rules-users@lists.jboss.org
Sent: Sun, October 3, 2010 10:51:08 PM
Subject: Re: [rules-users] fireUntilHalt and timing of rule activations
2010/10/4 Greg Barton greg_bar...@yahoo.com
If you don't have some way
rules-users@lists.jboss.org
Sent: Sun, October 3, 2010 10:51:08 PM
Subject: Re: [rules-users] fireUntilHalt and timing of rule activations
2010/10/4 Greg Barton greg_bar...@yahoo.com
If you don't have some way of associating the data with a particular Latch
it's easy to get overlap when
. This is necessary because there's no guarantee that
two Latch objects aren't in working memory at once. (Though you could create
a rule that enforces this.)
GreG
--- On Sat, 10/2/10, Norman C rent_my_t...@yahoo.com wrote:
From: Norman C rent_my_t...@yahoo.com
Subject: [rules-users] fireUntilHalt
, and that would be more clear, IMO. I'm curious to see of the
enabled trick would perform better, though.
GreG
--- On Sun, 10/3/10, Wolfgang Laun wolfgang.l...@gmail.com wrote:
From: Wolfgang Laun wolfgang.l...@gmail.com
Subject: Re: [rules-users] fireUntilHalt and timing of rule activations
To: Rules
Hi All,
In my app, I have a separate thread calling fireUntilHalt() continuously. I
have quite a few rules, and I am using salience extensively to control the
order
in which rules are executed. What I have seen (by adding an event listener) is
that as a new fact is inserted, various rules
, 10/2/10, Norman C rent_my_t...@yahoo.com wrote:
From: Norman C rent_my_t...@yahoo.com
Subject: [rules-users] fireUntilHalt and timing of rule activations
To: rules-users@lists.jboss.org
Date: Saturday, October 2, 2010, 10:22 AM
Hi All,
In my app, I have a separate thread calling
: Freitag, 13. August 2010 14:46
An: rules-users@lists.jboss.org
Betreff: Re: [rules-users] fireUntilHalt() and OSGi - CPU load
When invoking fireUntilHalt() for my StatefulKnowledgeSession, CPU load
rises to 25% (meaning one complete core on the quad-core machine).
I can confirm this issue. Below
34 matches
Mail list logo