7:28 a.m.
Hi,
I am getting null pointer exception when i retract objects from working
memory. please help me in resolving this problem....
my rule goes like this...
package com.moto.nms
import com.moto.nms.Event;
import com.adventnet.nms.topodb.ManagedObject;
import com.motorola.nmatg.nms.topology.ManagedEntity;
global com.moto.nms.Consecutive con; // Consecutive is an simple
class file which has two simple methods, getValue() and setValue().
rule "duplicate"
salience 29
when
e1 : Event( firsttime1 : time , severity1 : severity == 1 )
e2 : Event( firsttime2 : time > firsttime1 , severity == severity1 )
not Event( severity == -1 , time > firsttime1 , time < firsttime2)
then
System.out.println("matched the fact");
e1.setCompressionStatus("compress_"+con.getValue());
e2.setCompressionStatus("compress_"+con.getValue());
end
rule "duplicate_x"
salience 29
when
e1 : Event(firsttime1 : time , severity == 1 )
e2 : Event(firsttime2 : time > firsttime1 , severity == 1)
exists Event( severity == -1, time > firsttime1 , time < firsttime2)
then
System.out.println("matched 2nd fact");
con.setValue(con.getValue() +1);
end
exception is like this...
Caught Exceptionjava.lang.NullPointerException
java.lang.NullPointerException
at org.drools.reteoo.beta.DefaultRightMemory.remove(Unknown Source)
at org.drools.reteoo.BetaMemory.remove(Unknown Source)
at org.drools.reteoo.NotNode.retractObject(Unknown Source)
at org.drools.reteoo.ObjectSource.propagateRetractObject(Unknown Source)
at org.drools.reteoo.RightInputAdapterNode.retractTuple(Unknown Source)
at org.drools.reteoo.TupleSource.propagateRetractTuple(Unknown Source)
at org.drools.reteoo.NotNode.retractTuple(Unknown Source)
at org.drools.reteoo.TupleSource.propagateRetractTuple(Unknown Source)
at org.drools.reteoo.JoinNode.retractTuple(Unknown Source)
at org.drools.reteoo.LeftInputAdapterNode.retractObject(Unknown Source)
at org.drools.reteoo.ObjectSource.propagateRetractObject(Unknown Source)
at org.drools.reteoo.AlphaNode.retractObject(Unknown Source)
at org.drools.reteoo.ObjectSource.propagateRetractObject(Unknown Source)
at org.drools.reteoo.ObjectTypeNode.retractObject(Unknown Source)
at org.drools.reteoo.Rete.retractObject(Unknown Source)
at org.drools.reteoo.ReteooRuleBase.retractObject(Unknown Source)
at org.drools.reteoo.ReteooWorkingMemory.doRetract(Unknown Source)
at org.drools.common.AbstractWorkingMemory.retractObject(Unknown Source)
at org.drools.common.AbstractWorkingMemory.retractObject(Unknown Source)
at com.moto.nms.TestEvents3.retractAll(TestEvents3.java:219)
at com.moto.nms.TestEvents3.readRule(TestEvents3.java:158)
at com.moto.nms.TestEvents3.main(TestEvents3.java:242)
TestEvents3.java class is like this....
package com.moto.nms;
//related to IO..
import java.io.InputStreamReader;
import java.io.Reader;
import java.io.InputStream;
import java.util.List;
import java.util.Iterator;
//related to Drools..
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.compiler.PackageBuilder;
import org.drools.rule.Package;
import org.drools.WorkingMemory;
import org.drools.FactHandle;
import org.drools.FactException;
import com.moto.nms.Event;
import com.moto.nms.NMSEvent;
import com.moto.nms.TopoInterface1;
import com.moto.nms.GenerateEvents;
import com.adventnet.nms.topodb.ManagedObject;
import com.moto.nms.Consecutive;
public class TestEvents3 {
private Reader reader;
private RuleBase rulebase;
private WorkingMemory wm;
private List factHandles;
public TestEvents3(){
}
public void readRule(String readername) throws Exception{
InputStream str = null;
str = TestEvents.class.getResourceAsStream(readername);
if(str == null)
{
System.out.println("unable to read rule file");
return;
}
reader = new InputStreamReader(str); //read in the source
PackageBuilder builder = new PackageBuilder(); //building up the rule
package
builder.addPackageFromDrl(reader);
Package pkg = builder.getPackage(); //get the compiled package
rulebase = RuleBaseFactory.newRuleBase();
rulebase.addPackage( pkg ); //adding the package to the rule base
Consecutive con = new Consecutive();
wm = rulebase.newWorkingMemory();
wm.setGlobal("con", con);
System.out.println("\n\n"+System.currentTimeMillis());
Event ev1 = new Event(183, 1, "port02", "LOS",
System.currentTimeMillis());
//Thread.sleep(450);
Event ev9 = new Event(192, 1, "port02", "LOS",
System.currentTimeMillis());
//Thread.sleep(400);
Event ev10 = new Event(307, 1, "port02", "LOS",
System.currentTimeMillis());
Thread.sleep(500);
Event ev11= new Event(306, 1, "port02", "LOS",
System.currentTimeMillis());
Thread.sleep(200);
Event ev12= new Event(305, 1, "port02", "LOS",
System.currentTimeMillis());
Thread.sleep(250);
Event ev13= new Event(304, -1, "port02", "LOS",
System.currentTimeMillis());
Thread.sleep(600);
Event ev14= new Event(302, 1, "port02", "LOS",
System.currentTimeMillis());
Thread.sleep(200);
Event ev15= new Event(301, 1, "port02", "LOS",
System.currentTimeMillis());
Thread.sleep(200);
Event ev16= new Event(308, 1, "port02", "LOS",
System.currentTimeMillis());
wm.assertObject(ev1);
wm.assertObject(ev9);
wm.assertObject(ev10);
wm.assertObject(ev11);
wm.assertObject(ev12);
wm.assertObject(ev13);
wm.assertObject(ev14);
wm.assertObject(ev15);
wm.assertObject(ev16);
System.out.println("\n\n"+System.currentTimeMillis());
System.out.println("\n\nFiring rules...\n");
wm.fireAllRules();
factHandles = wm.getObjects();
System.out.println("\n\nAll the Objects in WOrking Memory are as
Follows...\n");
for(int i=0; i<factHandles.size(); i++)
{
System.out.println(factHandles.get(i));
}
System.out.println("The CompressionStatus of the events are...");
System.out.println(ev1.getCompressionStatus());
System.out.println(ev9.getCompressionStatus());
System.out.println(ev10.getCompressionStatus());
System.out.println(ev11.getCompressionStatus());
System.out.println(ev12.getCompressionStatus());
System.out.println(ev13.getCompressionStatus());
System.out.println(ev14.getCompressionStatus());
System.out.println(ev15.getCompressionStatus());
System.out.println(ev16.getCompressionStatus());
System.out.println("The DeletionStatus of the events are...");
System.out.println(ev1.getDeletionStatus());
System.out.println(ev9.getDeletionStatus());
System.out.println(ev10.getDeletionStatus());
System.out.println(ev11.getDeletionStatus());
System.out.println(ev12.getDeletionStatus());
System.out.println(ev13.getDeletionStatus());
System.out.println(ev14.getDeletionStatus());
System.out.println(ev15.getDeletionStatus());
System.out.println(ev16.getDeletionStatus());
Thread.sleep(1000);
System.out.println("Starting retracting....");
Thread.sleep(1000);
retractAll();
System.out.println(System.currentTimeMillis());
}
public void retractAll()
{
factHandles = wm.getFactHandles();
Iterator itr = factHandles.iterator();
if(factHandles == null)
{
System.out.println("invalid FactHandler List");
return;
}
System.out.println("size of fact handles..:"+factHandles.size());
while(itr.hasNext())
{
try{
FactHandle fh = (FactHandle)itr.next();
if(fh == null)
System.out.println("Here object is null, Cannot be retracted");
else
{
wm.retractObject(fh);
System.out.println("Retracted object : "+ fh);
}
}catch (FactException e){
e.printStackTrace();
}
}
return;
}
public static void main(String[] args){
TestEvents3 te = new TestEvents3();
try{
te.readRule("/AlarmSuppression.drl");
}catch(Exception ex){
System.out.println("Caught Exception" +ex);
ex.printStackTrace();}
}
}
Thanks,
RameshReddy,
Trainee,
Motorola India.
12:32 a.m.
New subject: How many objects we can assert into working memory maximum
Hi,
Is working memory size increases dynamically?? How many objects
we can assert into workingmemory? given, all the objects are matching
with rule in a drl file...
can anyone please tell me this...?
thanks,
Ramesh
1:22 a.m.
New subject: How many objects we can assert into working memory maximum
The answer is:
42.
Or, perhaps, the length of a piece of string.
It really varies with how much memory you want to throw at it, thats all
really. The effectiveness of the RETE network may also add some overhead.
I have heard of people pushing in millions of facts into one working memory,
but that would tend to be extreme - and it will use a lot of memory.
IN 3.2 there are some added efficiencies over 3.0, when it comes out.
On 2/27/07, Reddy Ramesh-in2259c <in2259c(a)motorola.com> wrote:
Hi,
Is working memory size increases dynamically?? How many objects we
can assert into workingmemory? given, all the objects are matching with rule
in a drl file...
can anyone please tell me this...?
thanks,
Ramesh
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
1:18 a.m.
New subject: How many objects we can assert into working memorymaximum
Hi all,
This is Ramesh Reddy, trainee, in Motorola India Electronics pvt ltd.
I have a rule something like this....,
package com.motorola.nmatg.nms.nfm.suppression
import com.motorola.nmatg.nms.nfm.suppression.ExtendedEvent;
/*
This rule compress duplicates
*/
rule "Compress"
salience 10
when
event_1 : ExtendedEvent ( moid1 : source , severity1 : severity ,
eventType1 : eventType , eventTime1 : time )
event_2 : ExtendedEvent ( moid2 : source , severity2 : severity ,
eventType2 : eventType , eventTime2 : time )
eval (
moid1.equals(moid2) &&
severity1.intValue() == severity2.intValue() &&
eventType1.equals(eventType2) &&
eventTime2.longValue() >= eventTime1.longValue()
)
then
event_1.setStatus("compress");
event_2.setStatus("compress");
end
This is the rule which i am using in my DRL file. I am asserting events
into working memory such that all the events are matching with the rule.
But i am unable to assert more than around 1000 events into
workingMemory, I am keep asserting events into working memory, by the
time it reaches the count to around 1000 events, it is throwing memory
out of bound exception. I increased heap size from default 64mb to
512mb. with this i could able to assert more 300 events thats it.
when i got this problem, i modified my rule in the following way,
rule "Compress"
salience 10
when
event_1 : ExtendedEvent ( moid1 : source , severity1 : severity ,
eventType1 : eventType , eventTime1 : time )
event_2 : ExtendedEvent ( source == moid1 , severity == severity1 ,
eventType == eventType1 , time >= eventTime1 )
then
event_1.setStatus("compress");
event_2.setStatus("compress");
end
If i write my rule like this, then i could able to assert more 500 event
objects. i.e i could able to assert in total around 1700 event objects
with this modified rule.
As per my understanding,
when we assert objects into working memory, pattern matching is
done at the time of assertion only, while this process, if we create
more variables in "when" part and using "eval" creating more
overhead(memory perspective) while pattern matching. When we assert
thousands of objects(events) into working memory, i think Drools engine
creates several objects internally(in rete network which i am not
aware), i think that would be the overhead.
But in my project, i need to work with around 15,000 event objects in
the working memory, of them, around 10,000 objects will match the rule.
Can any one in the group help me how to approach to solve this problem.
Is there anyway.. Ultimately, i have to work with 10000 events in
working memory, given all the events matches with the rule in DRL.
Thanks,
Ramesh
________________________________
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Michael Neale
Sent: Tuesday, February 27, 2007 12:52 PM
To: Rules Users List
Subject: Re: [rules-users] How many objects we can assert into working
memorymaximum
The answer is:
42.
Or, perhaps, the length of a piece of string.
It really varies with how much memory you want to throw at it, thats all
really. The effectiveness of the RETE network may also add some
overhead.
I have heard of people pushing in millions of facts into one working
memory, but that would tend to be extreme - and it will use a lot of
memory.
IN 3.2 there are some added efficiencies over 3.0, when it comes out.
On 2/27/07, Reddy Ramesh-in2259c <in2259c(a)motorola.com> wrote:
Hi,
Is working memory size increases dynamically?? How many
objects we can assert into workingmemory? given, all the objects are
matching with rule in a drl file...
can anyone please tell me this...?
thanks,
Ramesh
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
6:09 a.m.
New subject: How many objects we can assert into workingmemorymaximum
Hi...,
Can any one pls help me.... regarding my previous mail...
________________________________
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Reddy
Ramesh-in2259c
Sent: Wednesday, February 28, 2007 12:49 PM
To: Rules Users List
Subject: RE: [rules-users] How many objects we can assert into
workingmemorymaximum
Hi all,
I have a rule something like this....,
package com.motorola.nmatg.nms.nfm.suppression
import com.motorola.nmatg.nms.nfm.suppression.ExtendedEvent;
/*
This rule compress duplicates
*/
rule "Compress"
salience 10
when
event_1 : ExtendedEvent ( moid1 : source , severity1 : severity ,
eventType1 : eventType , eventTime1 : time )
event_2 : ExtendedEvent ( moid2 : source , severity2 : severity ,
eventType2 : eventType , eventTime2 : time )
eval (
moid1.equals(moid2) &&
severity1.intValue() == severity2.intValue() &&
eventType1.equals(eventType2) &&
eventTime2.longValue() >= eventTime1.longValue()
)
then
event_1.setStatus("compress");
event_2.setStatus("compress");
end
This is the rule which i am using in my DRL file. I am asserting events
into working memory such that all the events are matching with the rule.
But i am unable to assert more than around 1000 events into
workingMemory, I am keep asserting events into working memory, by the
time it reaches the count to around 1000 events, it is throwing memory
out of bound exception. I increased heap size from default 64mb to
512mb. with this i could able to assert more 300 events thats it.
when i got this problem, i modified my rule in the following way,
rule "Compress"
salience 10
when
event_1 : ExtendedEvent ( moid1 : source , severity1 : severity ,
eventType1 : eventType , eventTime1 : time )
event_2 : ExtendedEvent ( source == moid1 , severity == severity1 ,
eventType == eventType1 , time >= eventTime1 )
then
event_1.setStatus("compress");
event_2.setStatus("compress");
end
If i write my rule like this, then i could able to assert more 500 event
objects. i.e i could able to assert in total around 1700 event objects
with this modified rule.
As per my understanding,
when we assert objects into working memory, pattern matching is
done at the time of assertion only, while this process, if we create
more variables in "when" part and using "eval" creating more
overhead(memory perspective) while pattern matching. When we assert
thousands of objects(events) into working memory, i think Drools engine
creates several objects internally(in rete network which i am not
aware), i think that would be the overhead.
But in my project, i need to work with around 15,000 event objects in
the working memory, of them, around 10,000 objects will match the rule.
Can any one in the group help me how to approach to solve this problem.
Is there anyway.. Ultimately, i have to work with 10000 events in
working memory, given all the events matches with the rule in DRL.
Thanks,
Ramesh
________________________________
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Michael Neale
Sent: Tuesday, February 27, 2007 12:52 PM
To: Rules Users List
Subject: Re: [rules-users] How many objects we can assert into working
memorymaximum
The answer is:
42.
Or, perhaps, the length of a piece of string.
It really varies with how much memory you want to throw at it, thats all
really. The effectiveness of the RETE network may also add some
overhead.
I have heard of people pushing in millions of facts into one working
memory, but that would tend to be extreme - and it will use a lot of
memory.
IN 3.2 there are some added efficiencies over 3.0, when it comes out.
On 2/27/07, Reddy Ramesh-in2259c <in2259c(a)motorola.com> wrote:
Hi,
Is working memory size increases dynamically?? How many
objects we can assert into workingmemory? given, all the objects are
matching with rule in a drl file...
can anyone please tell me this...?
thanks,
Ramesh
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
6:41 a.m.
New subject: How many objects we can assert into working memorymaximum
Ramesh,
It is not easy to help you having only that much of information.
What I can assure you is that I personally had worked in the
development of a system where in production asserts more than 1 million
facts into working memory. So, it is not a soft/hard limitation in the
engine itself.
Your use case must be profiled to see where the memory is going.
Question: how much memory does your "ExtendedEvent" objects use? how
much the engine use? how much the rest of the application use?
On a rule writing tip, you realized by yourself that eval() is evil!!
and yet, you are not the only one that tried to use it... :) maybe we
should start a crusade against eval for people to be aware of how much
it hurts performance. :) We have to support it because some really
specific cases, need it, but it is not supposed to be used lightly.
So, going back to the point, 15000 facts is really not that much. But
the only way of understanding why you are having problems is profiling.
[]s
Edson
Reddy Ramesh-in2259c wrote:
Hi all,
This is Ramesh Reddy, trainee, in Motorola India Electronics pvt ltd.
I have a rule something like this....,
package com.motorola.nmatg.nms.nfm.suppression
import com.motorola.nmatg.nms.nfm.suppression.ExtendedEvent;
/*
This rule compress duplicates
*/
rule "Compress"
salience 10
when
event_1 : ExtendedEvent ( moid1 : source , severity1 : severity ,
eventType1 : eventType , eventTime1 : time )
event_2 : ExtendedEvent ( moid2 : source , severity2 : severity ,
eventType2 : eventType , eventTime2 : time )
eval (
moid1.equals(moid2) &&
severity1.intValue() == severity2.intValue() &&
eventType1.equals(eventType2) &&
eventTime2.longValue() >= eventTime1.longValue()
)
then
event_1.setStatus("compress");
event_2.setStatus("compress");
end
This is the rule which i am using in my DRL file. I am asserting
events into working memory such that all the events are matching with
the rule. But i am unable to assert more than around 1000 events into
workingMemory, I am keep asserting events into working memory, by the
time it reaches the count to around 1000 events, it is throwing memory
out of bound exception. I increased heap size from default 64mb to
512mb. with this i could able to assert more 300 events thats it.
when i got this problem, i modified my rule in the following way,
rule "Compress"
salience 10
when
event_1 : ExtendedEvent ( moid1 : source , severity1 : severity ,
eventType1 : eventType , eventTime1 : time )
event_2 : ExtendedEvent ( source == moid1 , severity == severity1 ,
eventType == eventType1 , time >= eventTime1 )
then
event_1.setStatus("compress");
event_2.setStatus("compress");
end
If i write my rule like this, then i could able to assert more 500
event objects. i.e i could able to assert in total around 1700 event
objects with this modified rule.
As per my understanding,
when we assert objects into working memory, pattern matching
is done at the time of assertion only, while this process, if we
create more variables in "when" part and using "eval" creating more
overhead(memory perspective) while pattern matching. When we assert
thousands of objects(events) into working memory, i think Drools
engine creates several objects internally(in rete network which i am
not aware), i think that would be the overhead.
But in my project, i need to work with around 15,000 event objects in
the working memory, of them, around 10,000 objects will match the rule.
Can any one in the group help me how to approach to solve this
problem. Is there anyway.. Ultimately, i have to work with 10000
events in working memory, given all the events matches with the rule
in DRL.
Thanks,
Ramesh
------------------------------------------------------------------------
*From:* rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] *On Behalf Of *Michael Neale
*Sent:* Tuesday, February 27, 2007 12:52 PM
*To:* Rules Users List
*Subject:* Re: [rules-users] How many objects we can assert into
working memorymaximum
The answer is:
42.
Or, perhaps, the length of a piece of string.
It really varies with how much memory you want to throw at it, thats
all really. The effectiveness of the RETE network may also add some
overhead.
I have heard of people pushing in millions of facts into one working
memory, but that would tend to be extreme - and it will use a lot of
memory.
IN 3.2 there are some added efficiencies over 3.0, when it comes out.
On 2/27/07, *Reddy Ramesh-in2259c* <in2259c(a)motorola.com
<mailto:in2259c@motorola.com>> wrote:
Hi,
Is working memory size increases dynamically?? How many
objects we can assert into workingmemory? given, all the objects
are matching with rule in a drl file...
can anyone please tell me this...?
thanks,
Ramesh
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org <mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
------------------------------------------------------------------------
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3124-6000
Mobile: +55 11 9218-4151
JBoss, a division of Red Hat @ www.jboss.com
6481
days inactive
6487
days old
5 comments
3 participants
participants (3)
-
Edson Tirelli -
Michael Neale -
Reddy Ramesh-in2259c