Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 724797 (BRMS-637)

Summary: NullPointerException in FromNode.destroyCreatedHandles
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Alessandro Lazarotti <alazarot>
Component: BRE (Expert, Fusion)Assignee: Nobody <nobody>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: unspecified   
Target Milestone: ---   
Target Release: BRMS 5.3.0.GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-637
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:14:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 724801    
Attachments:
Description Flags
00504048.zip none

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.
Comment 20 Red Hat Bugzilla 2025-02-10 03:14:03 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.