Bug 724797 (BRMS-637) - NullPointerException in FromNode.destroyCreatedHandles
Summary: NullPointerException in FromNode.destroyCreatedHandles
Keywords:
Status: VERIFIED
Alias: BRMS-637
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion)
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Nobody
QA Contact: Lukáš Petrovický
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks: BRMS-641
TreeView+ depends on / blocked
 
Reported: 2011-07-12 23:34 UTC by Alessandro Lazarotti
Modified: 2022-05-31 22:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
00504048.zip (505.49 KB, application/zip)
2011-07-13 21:22 UTC, Alessandro Lazarotti
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-637 0 None Closed NullPointerException in FromNode.destroyCreatedHandles 2012-05-04 02:01:43 UTC

Description Alessandro Lazarotti 2011-07-12 23:34:40 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007p3Un&sfdc.override=1
securitylevel_name: Public

I received this NullPointerException after upgrading to drools 5.1.1.  The NullPointerException is being thrown when the rule executes "update($build);" where $build is set in the LHS from a Build in working memory.  I'm not sure if the bug is that matches may be null and a null check needs to be added or if something else is going on causing the tuple to not be found.

Caused by: java.lang.NullPointerException
	at org.drools.reteoo.FromNode.destroyCreatedHandles(FromNode.java:336)
	at org.drools.reteoo.FromNode.retractLeftTuple(FromNode.java:326)
	at org.drools.reteoo.CompositeLeftTupleSinkAdapter.doPropagateRetractLeftTuple(CompositeLeftTupleSinkAdapter.java:238)
	at org.drools.reteoo.CompositeLeftTupleSinkAdapter.propagateRetractRightTuple(CompositeLeftTupleSinkAdapter.java:155)
	at org.drools.reteoo.JoinNode.retractRightTuple(JoinNode.java:151)
	at org.drools.reteoo.ModifyPreviousTuples.retractTuples(ModifyPreviousTuples.java:126)
	at org.drools.reteoo.EntryPointNode.modifyObject(EntryPointNode.java:176)
	at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1442)
	at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1349)
	at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:183)
	at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:196)
	at buildSchedulerV2.Rule_Combine_Builds_0.defaultConsequence(Rule_Combine_Builds_0.java:36)
	at buildSchedulerV2.Rule_Combine_Builds_0DefaultConsequenceInvoker.evaluate(Rule_Combine_Builds_0DefaultConsequenceInvoker.java:49)
	at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917)

Comment 1 Alessandro Lazarotti 2011-07-12 23:34:40 UTC
Link: Added: This issue Cloned from JBRULES-2796


Comment 2 Alessandro Lazarotti 2011-07-13 20:23:29 UTC
Help Desk Ticket Reference: Added: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007p3Un&sfdc.override=1


Comment 3 Alessandro Lazarotti 2011-07-13 21:22:10 UTC
Attachment: Added: 00504048.zip


Comment 4 Tihomir Surdilovic 2011-07-15 23:19:11 UTC
Link: Added: This issue depends BRMS-641


Comment 5 Tihomir Surdilovic 2011-07-15 23:49:53 UTC
Link: Removed: This issue depends BRMS-641 


Comment 6 Tihomir Surdilovic 2011-07-15 23:50:11 UTC
Link: Added: This issue is a dependency of BRMS-641


Comment 7 Rick Wagner 2011-07-19 15:22:05 UTC
It's been noted that Support Patch BRMS-599 fixes the symptons this bug exhibits.  If the customer agrees BRMS-599 is a good answer, we'll close this ticket.  

Comment 8 Rick Wagner 2011-08-25 13:21:25 UTC
gss_prioritized

The associated case is closed, so no special urgency for this case.

Comment 10 Lukáš Petrovický 2011-11-01 10:51:09 UTC
The related JIRA says this should be fixed already.


Note You need to log in before you can comment on or make changes to this bug.