Re: [rules-users] RightTupleIndexHashTable

2013-08-06 Thread Ming Fang
Using 5.6.0-SNAPSHOT we sometimes are seeing the error below.  It doesn't 
happen all the time. 
Is this just a harmless warning or is it a real problem?

11:26:53.829 WARN  [Thread-2] s.rule.constraint.MvelConstraint - Exception 
jitting: executionReport != this  $complianceId2 == complianceId2  
$realSeqNo  realSeqNo
java.lang.NullPointerException
at 
org.drools.base.defaultpkg.ClientFill1712121$getComplianceId2.getValue(Unknown 
Source)
at org.drools.base.ClassFieldReader.getValue(ClassFieldReader.java:87)
at org.drools.rule.Declaration.getValue(Declaration.java:233)
at 
org.drools.base.mvel.MVELCompilationUnit.updateFactory(MVELCompilationUnit.java:344)
at 
org.drools.base.mvel.MVELCompilationUnit.updateFactory(MVELCompilationUnit.java:289)
at 
org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62)
at 
org.drools.rule.constraint.MvelConditionEvaluator.ensureBranchEvaluation(MvelConditionEvaluator.java:120)
at 
org.drools.rule.constraint.MvelConditionEvaluator.ensureCompleteEvaluation(MvelConditionEvaluator.java:105)
at 
org.drools.rule.constraint.MvelConditionEvaluator.ensureCompleteEvaluation(MvelConditionEvaluator.java:93)
at 
org.drools.rule.constraint.MvelConditionEvaluator.getAnalyzedCondition(MvelConditionEvaluator.java:85)
at 
org.drools.rule.constraint.MvelConstraint.executeJitting(MvelConstraint.java:284)
at 
org.drools.rule.constraint.MvelConstraint.access$200(MvelConstraint.java:54)
at 
org.drools.rule.constraint.MvelConstraint$ConditionJitter.run(MvelConstraint.java:263)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
 

Sent from my iPhone

 On Aug 5, 2013, at 3:09 PM, Mark Proctor mproc...@codehaus.org wrote:
 
 
 On 5 Aug 2013, at 19:48, Ming Fang mingf...@mac.com wrote:
 
 Version 5.6.0-SNAPSHOT fixes the problem. 
 We're experiencing this problem in our Production environment and needs to 
 address it as soon as possible. 
 
 When is 5.6.0 scheduled to be released?
 We've been trying to schedule a release for some time now - but community 
 releases are best effort, and a new bug that needs fixing keeps coming up. 
 I'd say realistically I hope within next two weeks, but cannot guarantee that.
 
 Mark
 
 Sent from my iPhone
 
 On May 11, 2013, at 4:56 PM, Davide Sottara dso...@gmail.com wrote:
 
 Did you try 5.6.0-SNAPSHOT? 
 Many possibly related bugs have been fixed there, and it's about to be 
 released as 5.6.0.Final.
 On the other hand, if you could help us identify your issue by providing 
 some more context,
 we'd try to make sure that a fix is included in 5.6.0.Final
 Thanks
 Davide 
 
 On 05/11/2013 02:14 PM, Ming Fang wrote:
 We did not explicitly enable multithread mode, unless it's on by default. 
 Also we're only using Drools in a single thread.
 
 Sent from my iPad
 
 On May 11, 2013, at 1:05 PM, Mark Proctor mproc...@codehaus.org wrote:
 
 It's used for indexing in joins.
 
 It looks like you are using the experimental multi-threading mode, I'd 
 recommend you disable that, and try the latest 5.6.0.SNAPSHOT builds if 
 you have problems.
 
 Mark
 On 11 May 2013, at 17:01, Ming Fang mingf...@mac.com wrote:
 
 What is the purpose of RightTupleIndexHashTable?
 We are getting the exception below but unable to come up with a self 
 contained unit test to demonstrate the problem.
 
 Caused by: java.lang.NullPointerException: null
 at 
 org.drools.core.util.index.RightTupleIndexHashTable.removeAdd(RightTupleIndexHashTable.java:344)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at org.drools.reteoo.JoinNode.modifyRightTuple(JoinNode.java:224) 
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$ModifyToSinkAction.execute(PropagationQueuingNode.java:513)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:280)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:588)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:993)
  [drools-core-5.5.0.Final.jar:5.5.0.Final]
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
 
 
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users

Re: [rules-users] RightTupleIndexHashTable

2013-08-06 Thread Ming Fang
I opened a Jira drools-211 and attached a self contained test case. 
It's caused by a race condition so you may have to try a couple of times to hit 
the error. 

Sent from my iPhone

 On Aug 6, 2013, at 12:20 PM, Mario Fusco mario.fu...@gmail.com wrote:
 
 Something in the middle. That warning is saying that for some reason drools
 isn't able to jit a constraint, i.e. to create a compiled constraint from an
 interpreted one. This is harmless in the sense that when this happens the
 compiled constraint gets automatically discarded and it continues being
 evaluated in interpreted mode. However interpreted constraints are slower
 than compiled ones, so it could be interesting to figure out why this is
 happening in your case. Do you have a test case that could allow me to
 reproduce this problem?
 
 Regards,
 Mario
 
 
 
 --
 View this message in context: 
 http://drools.46999.n3.nabble.com/rules-users-RightTupleIndexHashTable-tp4023782p4025375.html
 Sent from the Drools: User forum mailing list archive at Nabble.com.
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] RightTupleIndexHashTable

2013-08-05 Thread Ming Fang
Version 5.6.0-SNAPSHOT fixes the problem. 
We're experiencing this problem in our Production environment and needs to 
address it as soon as possible. 

When is 5.6.0 scheduled to be released?

Sent from my iPhone

 On May 11, 2013, at 4:56 PM, Davide Sottara dso...@gmail.com wrote:
 
 Did you try 5.6.0-SNAPSHOT? 
 Many possibly related bugs have been fixed there, and it's about to be 
 released as 5.6.0.Final.
 On the other hand, if you could help us identify your issue by providing some 
 more context,
 we'd try to make sure that a fix is included in 5.6.0.Final
 Thanks
 Davide 
 
 On 05/11/2013 02:14 PM, Ming Fang wrote:
 We did not explicitly enable multithread mode, unless it's on by default. 
 Also we're only using Drools in a single thread.
 
 Sent from my iPad
 
 On May 11, 2013, at 1:05 PM, Mark Proctor mproc...@codehaus.org wrote:
 
 It's used for indexing in joins.
 
 It looks like you are using the experimental multi-threading mode, I'd 
 recommend you disable that, and try the latest 5.6.0.SNAPSHOT builds if you 
 have problems.
 
 Mark
 On 11 May 2013, at 17:01, Ming Fang mingf...@mac.com wrote:
 
 What is the purpose of RightTupleIndexHashTable?
 We are getting the exception below but unable to come up with a self 
 contained unit test to demonstrate the problem.
 
 Caused by: java.lang.NullPointerException: null
 at 
 org.drools.core.util.index.RightTupleIndexHashTable.removeAdd(RightTupleIndexHashTable.java:344)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at org.drools.reteoo.JoinNode.modifyRightTuple(JoinNode.java:224) 
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$ModifyToSinkAction.execute(PropagationQueuingNode.java:513)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:280)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:588)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:993)
  [drools-core-5.5.0.Final.jar:5.5.0.Final]
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
 
 
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
 
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

[rules-users] RightTupleIndexHashTable

2013-05-11 Thread Ming Fang
What is the purpose of RightTupleIndexHashTable?
We are getting the exception below but unable to come up with a self contained 
unit test to demonstrate the problem.

Caused by: java.lang.NullPointerException: null
at 
org.drools.core.util.index.RightTupleIndexHashTable.removeAdd(RightTupleIndexHashTable.java:344)
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
at org.drools.reteoo.JoinNode.modifyRightTuple(JoinNode.java:224) 
~[drools-core-5.5.0.Final.jar:5.5.0.Final]
at 
org.drools.reteoo.PropagationQueuingNode$ModifyToSinkAction.execute(PropagationQueuingNode.java:513)
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
at 
org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:280)
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
at 
org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:588)
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
at 
org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:993)
 [drools-core-5.5.0.Final.jar:5.5.0.Final]___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

Re: [rules-users] RightTupleIndexHashTable

2013-05-11 Thread Ming Fang
Can you please point to any documentation on disabling the experimental mode?


Sent from my iPhone

On May 11, 2013, at 1:05 PM, Mark Proctor mproc...@codehaus.org wrote:

 It's used for indexing in joins.
 
 It looks like you are using the experimental multi-threading mode, I'd 
 recommend you disable that, and try the latest 5.6.0.SNAPSHOT builds if you 
 have problems.
 
 Mark
 On 11 May 2013, at 17:01, Ming Fang mingf...@mac.com wrote:
 
 What is the purpose of RightTupleIndexHashTable?
 We are getting the exception below but unable to come up with a self 
 contained unit test to demonstrate the problem.
 
 Caused by: java.lang.NullPointerException: null
 at 
 org.drools.core.util.index.RightTupleIndexHashTable.removeAdd(RightTupleIndexHashTable.java:344)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at org.drools.reteoo.JoinNode.modifyRightTuple(JoinNode.java:224) 
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$ModifyToSinkAction.execute(PropagationQueuingNode.java:513)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:280)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:588)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:993)
  [drools-core-5.5.0.Final.jar:5.5.0.Final]
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
 
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

Re: [rules-users] RightTupleIndexHashTable

2013-05-11 Thread Ming Fang
We did not explicitly enable multithread mode, unless it's on by default. 
Also we're only using Drools in a single thread.

Sent from my iPad

On May 11, 2013, at 1:05 PM, Mark Proctor mproc...@codehaus.org wrote:

 It's used for indexing in joins.
 
 It looks like you are using the experimental multi-threading mode, I'd 
 recommend you disable that, and try the latest 5.6.0.SNAPSHOT builds if you 
 have problems.
 
 Mark
 On 11 May 2013, at 17:01, Ming Fang mingf...@mac.com wrote:
 
 What is the purpose of RightTupleIndexHashTable?
 We are getting the exception below but unable to come up with a self 
 contained unit test to demonstrate the problem.
 
 Caused by: java.lang.NullPointerException: null
 at 
 org.drools.core.util.index.RightTupleIndexHashTable.removeAdd(RightTupleIndexHashTable.java:344)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at org.drools.reteoo.JoinNode.modifyRightTuple(JoinNode.java:224) 
 ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$ModifyToSinkAction.execute(PropagationQueuingNode.java:513)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:280)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:588)
  ~[drools-core-5.5.0.Final.jar:5.5.0.Final]
 at 
 org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:993)
  [drools-core-5.5.0.Final.jar:5.5.0.Final]
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
 
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

[rules-users] documentation on rule extends keyword

2012-09-26 Thread Ming Fang
Where can I find documentation on extending rules using the 'extends' keyword?
The official documentation doesn't even list that as a keyword.
I only found out about it by accident here 
http://blog.athico.com/2012/09/conditional-named-consequences-in.html

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


[rules-users] problem binding variable to map value

2012-02-09 Thread Ming Fang
Below is a very simple rule that binds a variable to a map value...

rule how many times is map.get() called?

   when
   p:Parameter(
   $value:tags[1]==1,
   $value == 1,
   $value != 2,
   $value != null,
   $value in (1,2)
   )
   then
   System.out.println(value= + $value);
end

The problem is map.get() is called 6 times when executing this rule using a 
Stateless session.
To test this I implement a mock Map that the get(key) simply returns the key. 
So in this example tags[1] return 1.
And in the get() I simply print a test message to see how many times it's been 
called.
Here is the sequence...

1x = tags[1]
2x = tags[1] == 1
3x = $value == 1
4x = $value != 2
5x = $value != null
and most surprisingly none for $value in (1,2)
but
6x == System.out.println(value=+$value)

Is this a bug?
It's a huge problem for my application since the call to get() is expensive for 
my map implementation.

Thanks
--ming
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Drools 5.1M2

2010-05-24 Thread Ming Fang
Mark,

The tests can't run because the drools-camel module has a dependency on spring 
2.5.5.
This version is then mixed with version 2.5.6 from other dependencies.
Simple fix is to change drools-camel to use spring 2.5.6.

But we should really be using Maven dependency management at the root level to 
avoid this problem.
In general there should not be any version numbers in any of the sub-modules.

But even after I got the test to run there is now an assertion failure in 
assertTrue(response.indexOf(ns2:namesanta/ns2:name)  -1);
I'll look into it after my day job.

--ming
 
On May 23, 2010, at 11:00 PM, Mark Proctor wrote:

 On 23/05/2010 08:16, Geoffrey De Smet wrote:
 
 Planner's examples in environmentMode DEBUG are not spotting any more 
 bugs in the statefull working memory.
 I ran examination on 32 configs last night which did over 10 million 
 fireAllRules without a single deviation.
 
 Trunk (5.1.M2-SNAPSHOT) is looking very good now :) and fast!
   
 Toni has tagged it ready to release, but is reporting build problems for 
 different platforms:
 In OSX:
   testJaxbInsertCommand(org.drools.server.service.KnowledgeServiceSoapTest)
   testBothsessions(org.drools.server.service.KnowledgeServiceSoapTest)
   testJaxbInsertCommand(org.drools.server.service.KnowledgeServiceRestTest)
   testBothsessions(org.drools.server.service.KnowledgeServiceRestTest)
  
 In RHEL:
 testOsgiPlatformStarts(org.drools.osgi.integrationtests.SimpleOsgiTest)
 testOsgiEnvironment(org.drools.osgi.integrationtests.SimpleOsgiTest)
 testCompiler(org.drools.osgi.integrationtests.SimpleOsgiTest)
 testDecisionTable(org.drools.osgi.integrationtests.SimpleOsgiTest)
 
 If anyone wants to help speed up drools delivey, please test on your platform 
 and submit any patches necessary to get it working.
 
 Mark

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] dynamic temporal parameters

2009-11-17 Thread Ming Fang
Mark,

Are there plans to support this in the future?
Should I submit a Jira?

--Ming

On Nov 17, 2009, at 4:32 AM, Mark Proctor mproc...@codehaus.org wrote:

 Ming Fang wrote:
 Is it possible to make temporal parameters dynamic by using bound  
 variables?
 Example:
EventA( this after[ $later ] $eventB)

 Currently, no.

 Mark
 --ming
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users





 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


[rules-users] dynamic temporal parameters

2009-11-16 Thread Ming Fang
Is it possible to make temporal parameters dynamic by using bound variables?
Example:
EventA( this after[ $later ] $eventB)

--ming
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Drools 4.0.7 - call for testers

2008-04-25 Thread Ming Fang

Please look into JBRULES-1572.
It is a race condition that is a blocker for me.

--Ming

On Apr 25, 2008, at 2:32 PM, Mark Proctor [EMAIL PROTECTED] wrote:

Please everyone help QA 4.0.x branch for regressions, which becomes  
4.0.7, especially the eclipse and mvel stuff. We really want to try  
and put this out monday/tuesday next week.


Mark
Mark Proctor wrote:

Emilian Pascalau wrote:

Do you have some test plans or do you just think of ad-hoc testing.
Emilian
We have a large set of unit/integration tests, beyond that nothing  
specific. We suggest you make sure that it works for you're use  
cases, without issue. We don't want people testing after the  
release and then moaning when they find X bug.


Mark


Mark Proctor wrote:
I'd also stress to please test the eclipse plugin, both 3.2 and  
3.3. Let's try and get out a quality 4.0.7 release for everyone,  
but we need your help :)


Mark
Edson Tirelli wrote:


   All,

   We are about to release Drools 4.0.7, but we want to improve  
QA for the community version. We have a good amount of unit and  
integration tests, but we would like to ask those of you using  
Drools 4.0.x to checkout and try 4.0.7 before we do the official  
release, in order to ensure 4.0.7 covers your use case. This  
way, if by any chance you find a problem or regression, we can  
address it and include in 4.0.7 version.


   To checkout the code:

http://anonsvn.labs.jboss.com/labs/jbossrules/branches/4.0.x/

   Instructions on how to build are in the manual, but being  
short, you need maven 2.0.8 and you should run:


mvn -Ddocumentation -Declipse clean install

   If you have any problems with that, check the manual.

   We are setting a short deadline. We will wait for reports  
until end of day tomorrow, so hurry up. We are not sure at this  
point if we will release another community version in the 4.0.x  
series or the next release will be 5.0.0, so if you use drools  
4.0.x, it is advisable you take the time to do this check.


   Thanks a lot
 Edson -- Edson Tirelli
JBoss Drools Core Development
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com http:// 
www.jboss.com
--- 
--- 
--


___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



--- 
--- 
--


___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Sudoku Example Errors

2007-05-25 Thread Ming Fang

Michael,

This is the example in the drools-examples directory,  
org.drools.examples.sudoku.SudokuExample.
I'm running latest code from the repository using Intellij, JDK 1.5  
on OS X.


--ming

On May 25, 2007, at 12:48 AM, Michael Neale wrote:

Errors like that are not normal, and definitely indicates a bug (ie  
not a compile error or anything - not something you should have to  
debug). So some more information is needed like versions, how you  
are running it, where the example came from etc (as there are a few  
versions floating around).


On 5/25/07, Ming Fang [EMAIL PROTECTED] wrote:
Hi,
I'm getting many of these errors when running the Sudoku Example

java.lang.NullPointerException
at org.drools.reteoo.ReteTuple.get(ReteTuple.java:71)
at org.drools.common.InstanceNotEqualsConstraint
$InstanceNotEqualsConstraintContextEntry.updateFromTuple
(InstanceNotEqualsConstraint.java:112)
at org.drools.common.TripleBetaConstraints.updateFromTuple
(TripleBetaConstraints.java:146)
at org.drools.reteoo.NotNode.assertTuple(NotNode.java:108)
at  
org.drools.reteoo.SingleTupleSinkAdapter.propagateAssertTuple

(SingleTupleSinkAdapter.java:29)
at org.drools.reteoo.NotNode.assertTuple(NotNode.java :121)
at  
org.drools.reteoo.SingleTupleSinkAdapter.propagateAssertTuple

(SingleTupleSinkAdapter.java:29)
at org.drools.reteoo.NotNode.assertTuple(NotNode.java:121)
at
org.drools.reteoo.CompositeTupleSinkAdapter.createAndPropagateAssertTu 
pl

e(CompositeTupleSinkAdapter.java:73)
at org.drools.reteoo.LeftInputAdapterNode.assertObject
(LeftInputAdapterNode.java:144)
at  
org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject

(CompositeObjectSinkAdapter.java:317)
at org.drools.reteoo.ObjectTypeNode.assertObject 
(ObjectTypeNode.java:

183)
at org.drools.reteoo.Rete.assertObject(Rete.java:121)
at org.drools.reteoo.ReteooRuleBase.assertObject  
(ReteooRuleBase.java:

201)
at org.drools.reteoo.ReteooWorkingMemory.doAssertObject
(ReteooWorkingMemory.java:70)
at org.drools.common.AbstractWorkingMemory.assertObject
(AbstractWorkingMemory.java :735)
at org.drools.base.DefaultKnowledgeHelper.assertObject
(DefaultKnowledgeHelper.java:72)
at org.drools.base.DefaultKnowledgeHelper.assertObject
(DefaultKnowledgeHelper.java:66)
at
org.drools.examples.sudoku.Rule_Rule_1__If_a_field_has_the_value_0__it 
_i

s_empty__remove_it_and_insert_the_PossibleValues_0.consequence
(Rule_Rule_1__If_a_field_has_the_value_0__it_is_empty__remove_it_and_i 
ns

ert_the_PossibleValues_0.java:8)
at
org.drools.examples.sudoku.Rule_Rule_1__If_a_field_has_the_value_0__it 
_i
s_empty__remove_it_and_insert_the_PossibleValues_0ConsequenceInvoker.e 
va

luate
(Rule_Rule_1__If_a_field_has_the_value_0__it_is_empty__remove_it_and_i 
ns

ert_the_PossibleValues_0ConsequenceInvoker.java:22)
at org.drools.common.DefaultAgenda.fireActivation 
(DefaultAgenda.java:

497)
at org.drools.common.DefaultAgenda.fireNextItem 
(DefaultAgenda.java :461)

at org.drools.common.AbstractWorkingMemory.fireAllRules
(AbstractWorkingMemory.java:372)
at org.drools.common.AbstractWorkingMemory.fireAllRules
(AbstractWorkingMemory.java:353)
at org.drools.examples.sudoku.SudokuExample.testWithInput
(SudokuExample.java:52)
at org.drools.examples.sudoku.SudokuExample.main 
(SudokuExample.java:94)



Besides the fact that these errors are naturally bad,
this points out the issue of Drools being very difficult debug when
bad things happen.
Can somebody give some tips of Drool debugging techniques?

Thanks,
--ming
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users