[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3234:
--------------------------------------------------
Alessandro Lazarotti <alazarot(a)redhat.com> made a comment on [bug
809302|https://bugzilla.redhat.com/show_bug.cgi?id=809302]
In the last activation, the tuple.getObject() is null at
RuleTerminalNode.createActivations, so we have the NPE. It happens for Drools 5.3+ and
BRMS 5.2+ (before these versions the algorithm had used the method
"modifyLeftTuple" with a different implementation instead of
createActivations).
Using a null checker in createActivation (look the my proposed patch attached) fixes this
issue and the test attached in JBRULES-3234 works as expected. I've sent to customer a
hotfix (temporary) using this fix and his code is working as well. However a better
solution is check with Edson if tuple.getObject() should really be null in that point or
not, maybe something wrong is happen in the new nodes that implements LeftTuple.
Customer is waiting an official patch for this issue ASAP.
NPE while creating activations if a fact is modified by multiple
prior consequences
------------------------------------------------------------------------------------
Key: JBRULES-3234
URL:
https://issues.jboss.org/browse/JBRULES-3234
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert), drools-core (flow)
Affects Versions: 5.3.0.CR1
Reporter: Jamie Shaw
Assignee: Edson Tirelli
Priority: Critical
Fix For: 5.3.1.Final, 5.4.0.Beta1
Attachments: Drools runtimes.png, JBRULES-3234.zip, nullpointer.txt, rulest.txt,
Test output.txt
I receive an NPE when attempting to modify a fact in a rule consequence if multiple prior
rules have modified the same fact.
It appears to involve the interaction between 3 rules, each of which is in a different
agenda group. For background, this is a fraud detection application. Under certain
conditions, we need to look up additional customer information. Some rules are run to
determine whether the lookup is required and then another rule actually does the lookup.
In this case:
Rule 021 says if the order is small, set the lookup flag on the customer fact to false
Rule 042B says if the order is from a 'bad' country, set the lookup flag on the
customer fact to true
Rule 022 says if the lookup flag is true, do the lookup, set the results on the customer
flag and set the lookup flag on the customer fact
If rule 021 fires alone, then 022 does not fire and all is well.
If rule 042B fires alone, then 022 fires and all is well.
If 021 fires to turn off the lookup AND 042B fires to turn on the lookup, then 022 gets
and NPE.
As Edson suspected, the item is null and the 'rule' variable points to rule 021.
Each rule involved is in a different agenda group.
This works in 5.2.0.Final, but breaks in 5.3.0.CR1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira