[rules-users] RightTupleIndexHashTable

[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 <mproctor at codehaus.org> wrote:
> 
> 
>> On 5 Aug 2013, at 19:48, Ming Fang <mingfang at 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 <dsotty at 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 <mproctor at 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 <mingfang at 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 at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/rules-users
>>>>> _______________________________________________
>>>>> rules-users mailing list
>>>>> rules-users at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/rules-users
>>>> 
>>>> 
>>>> _______________________________________________
>>>> rules-users mailing list
>>>> rules-users at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/rules-users
>>> 
>>> _______________________________________________
>>> rules-users mailing list
>>> rules-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/rules-users
>> _______________________________________________
>> rules-users mailing list
>> rules-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-users
> 
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20130806/8e5514dd/attachment-0001.html