[JBoss JIRA] (JBRULES-3234) NPE while creating activations if a fact is modified by multiple prior consequences
2:41 p.m.
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: Mark Proctor
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
2:48 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Jamie Shaw updated JBRULES-3234:
--------------------------------
Attachment: rulest.txt
This is a snippet from my rules file containing just the 3 problem rules.
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: Mark Proctor
Attachments: rulest.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
3:21 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Edson Tirelli reassigned JBRULES-3234:
--------------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
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
Attachments: rulest.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
3:23 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Edson Tirelli updated JBRULES-3234:
-----------------------------------
Priority: Critical (was: Major)
Forum Reference:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...
(was:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...)
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
Attachments: rulest.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
4:24 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Jamie Shaw updated JBRULES-3234:
--------------------------------
Attachment: JBRULES-3234.zip
Here's an Eclipse project containing an extremely simple example that demonstrates the
behavior. Setting isBuyer to 'true' causes the error and setting it to
'false' does not.
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
Attachments: JBRULES-3234.zip, rulest.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
4:28 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Jamie Shaw commented on JBRULES-3234:
-------------------------------------
I made a mistake in the description - the 3 rules are not all in different agenda groups.
021 and 042B are in one group and 022 is in another one.
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
Attachments: JBRULES-3234.zip, rulest.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
9:32 a.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Jamie Shaw updated JBRULES-3234:
--------------------------------
Steps to Reproduce: See attached example. (was: I haven't been able to create a
stand-alone example, but the description above outlines the scenario. I will try again to
create a stand-alone example and I'll attach it to this ticket if I'm
successful.)
Forum Reference:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...
(was:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...)
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
Attachments: JBRULES-3234.zip, rulest.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
12:07 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Edson Tirelli resolved JBRULES-3234.
------------------------------------
Fix Version/s: 5.4.0.Beta1
5.3.1.Final
Resolution: Done
Tested with both 5.3.0.final and 5.4.0.beta2 and problem no longer happens. I am closing
this ticket. If you still see the problem, please reopen the ticket and let me know.
Thank you for reporting.
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.4.0.Beta1, 5.3.1.Final
Attachments: JBRULES-3234.zip, rulest.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
12:07 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Edson Tirelli closed JBRULES-3234.
----------------------------------
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: JBRULES-3234.zip, rulest.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
2:42 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Jamie Shaw reopened JBRULES-3234:
---------------------------------
I've tested it in 5.3.0 and 5.4.0 Beta1 and I'm still seeing the same error.
I've attached a screenshot showing the Drools runtimes I've defined on my machine.
The test case attached to this ticket only runs cleanly under 5.2.0. I've also
attached the stack trace from the test failure.
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: JBRULES-3234.zip, rulest.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
2:50 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Jamie Shaw updated JBRULES-3234:
--------------------------------
Attachment: Drools runtimes.png
Drools runtimes defined on my machine
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, rulest.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
2:52 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Jamie Shaw updated JBRULES-3234:
--------------------------------
Attachment: Test output.txt
The output from my failed test run, including stack trace.
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, 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
9:51 a.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Cyril Sochor commented on JBRULES-3234:
---------------------------------------
I have same problem with drools 5.3.0Final and 5.4.0Beta2. My exception:
Exception in thread "Thread-4" org.drools.RuntimeDroolsException: Unexpected
exception executing action
org.drools.rule.SlidingTimeWindow$BehaviorExpireWMAction@1161fded
at
org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:977)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:315)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:291)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:845)
at
org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:255)
at
org.drools.runtime.pipeline.impl.StatefulKnowledgeSessionInsertStage.receive(StatefulKnowledgeSessionInsertStage.java:35)
at org.drools.runtime.pipeline.impl.BaseEmitter.emit(BaseEmitter.java:47)
at
org.drools.runtime.pipeline.impl.JmsUnwrapMessageObject.receive(JmsUnwrapMessageObject.java:35)
at org.drools.runtime.pipeline.impl.BaseEmitter.emit(BaseEmitter.java:47)
at
org.drools.runtime.pipeline.impl.StatefulKnowledgeSessionPipelineImpl.insert(StatefulKnowledgeSessionPipelineImpl.java:56)
at
org.drools.runtime.pipeline.impl.JmsMessenger$JmsMessengerRunner.run(JmsMessenger.java:149)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at
org.drools.reteoo.RuleTerminalNode.createActivations(RuleTerminalNode.java:276)
at org.drools.reteoo.RuleTerminalNode.modifyLeftTuple(RuleTerminalNode.java:326)
at
org.drools.reteoo.SingleLeftTupleSinkAdapter.propagateModifyChildLeftTuple(SingleLeftTupleSinkAdapter.java:260)
at
org.drools.reteoo.AccumulateNode.evaluateResultConstraints(AccumulateNode.java:694)
at
org.drools.reteoo.ReteooWorkingMemory$EvaluateResultConstraints.execute(ReteooWorkingMemory.java:584)
at
org.drools.common.PropagationContextImpl.evaluateActionQueue(PropagationContextImpl.java:265)
at org.drools.rule.SlidingTimeWindow.expireTuples(SlidingTimeWindow.java:182)
at
org.drools.rule.SlidingTimeWindow$BehaviorExpireWMAction.execute(SlidingTimeWindow.java:464)
at
org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:975)
... 12 more
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, 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
3:41 a.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Emanuele Mariani updated JBRULES-3234:
--------------------------------------
Attachment: nullpointer.txt
Hi,
we have the same problem as well with the 5.3.1.Final or 5.4.0Beta2. The 5.3.0.Final solve
a big problem about the memory leak but with this issue we can't upgrade to the now
version.
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
3:43 a.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Emanuele Mariani edited comment on JBRULES-3234 at 3/5/12 4:42 AM:
-------------------------------------------------------------------
Hi,
we have the same problem as well with the 5.3.1.Final or 5.4.0Beta2. The 5.3.0.Final solve
a big problem about the memory leak but with this issue we can't upgrade to the now
version.
Below the full stack trace.
Thanks in advance.
Bye
was (Author: marlele):
Hi,
we have the same problem as well with the 5.3.1.Final or 5.4.0Beta2. The 5.3.0.Final solve
a big problem about the memory leak but with this issue we can't upgrade to the now
version.
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
11:04 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration updated JBRULES-3234:
---------------------------------------------
Bugzilla Update: Perform
Forum Reference:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...
(was:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...)
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
11:04 p.m.
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration updated JBRULES-3234:
---------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=809302
Forum Reference:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...
(was:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...)
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
11:04 p.m.
[
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]
Description of problem:
A NPE in terminal nodes can be raised if a same fact is updated in different
agenda/rulefow groups
Version-Release number of selected component (if applicable):
BRE from JBoss Enterprise BRMS 5.2
How reproducible:
Steps to Reproduce:
1.Unzip the attached file
2.Import the project in JBDS
3.Run the class com.fraud.rule.test.TestDroolsBug.java
Actual results:
running
021 firing
042B firing
022 firing
Exception in thread "main" org.drools.runtime.rule.ConsequenceException: rule:
Rule 022 - Load Buyer Activity
at
org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1101)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1029)
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1251)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:737)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:701)
at
org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:218)
at com.fraud.rule.test.TestDroolsBug.main(TestDroolsBug.java:28)
Caused by: java.lang.NullPointerException
at org.drools.reteoo.RuleTerminalNode.createActivations(RuleTerminalNode.java:276)
at org.drools.reteoo.RuleTerminalNode.modifyLeftTuple(RuleTerminalNode.java:326)
at
org.drools.reteoo.SingleLeftTupleSinkAdapter.propagateModifyChildLeftTuple(SingleLeftTupleSinkAdapter.java:273)
Expected results:
running
021 firing
042B firing
022 firing
done
Additional info:
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
11:18 p.m.
[
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]
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
11:21 p.m.
[
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]
A simple patch checking the null value
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
11:37 p.m.
[
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]
Technical note added. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
New Contents:
PRODUCT NAME:
JBoss Enterprise BRMS
VERSION:
5.2.0
SHORT DESCRIPTION:
NPE while creating activations if a fact is modified by prior consequences
LONG DESCRIPTION:
A NPE in terminal nodes can be raised if a same fact is updated in different
agenda/rulefow groups
MANUAL INSTALL INSTRUCTIONS:
To install this patch replace the following with the jars included in this patch:
For BRMS Manager :
$JBOSS_HOME/jboss-as/server/$PROFILE/jboss-brms.war/WEB-INF/lib/drools-core-5.2.0.BRMS.jar
For BRMS Engine :
The drools-core-5.2.0.BRMS.jar included with your application.
COMPATIBILITY:
DEPENDENCIES:
N/A
SUPERSEDES:
N/A
SUPERSEDED BY:
N/A
CREATOR:
Alessandro Lazarotti
DATE:
04/03/2012
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
11:39 p.m.
[
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
11:39 p.m.
[
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]
Technical note updated. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
Diffed Contents:
@@ -8,10 +8,8 @@
A NPE in terminal nodes can be raised if a same fact is updated in different
agenda/rulefow groups
MANUAL INSTALL INSTRUCTIONS:
To install this patch replace the following with the jars included in this patch:
- For BRMS Manager :
-
$JBOSS_HOME/jboss-as/server/$PROFILE/jboss-brms.war/WEB-INF/lib/drools-core-5.2.0.BRMS.jar
- For BRMS Engine :
- The drools-core-5.2.0.BRMS.jar included with your application.
+ For BRMS Manager:
$JBOSS_HOME/jboss-as/server/$PROFILE/jboss-brms.war/WEB-INF/lib/drools-core-5.2.0.BRMS.jar
+ For BRMS Engine: The drools-core-5.2.0.BRMS.jar included with your application.
COMPATIBILITY:
DEPENDENCIES:
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
7:33 a.m.
New subject: [JBoss JIRA] (JBRULES-3234) NPE on modify when using lock-on-active after assert
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Mark Proctor updated JBRULES-3234:
----------------------------------
Summary: NPE on modify when using lock-on-active after assert (was: NPE
while creating activations if a fact is modified by multiple prior consequences )
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=809302 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=809302)
Forum Reference:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...
(was:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...)
The assert would get blocked, due to lock on active. So we'd have a fully matched rule
with no AgendaItem. The later modify would expect there to be an AgendaItem as it's
fully matched.
While i could have just done a null check, I changed this to just add a Boolean object if
blocked and check for that. A null check is broader and might mask other issues.
NPE on modify when using lock-on-active after assert
----------------------------------------------------
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.4.0.Final
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
7:33 a.m.
New subject: [JBoss JIRA] (JBRULES-3234) NPE on modify when using lock-on-active after assert
[
https://issues.jboss.org/browse/JBRULES-3234?page=com.atlassian.jira.plug...
]
Mark Proctor closed JBRULES-3234.
---------------------------------
Assignee: Mark Proctor (was: Edson Tirelli)
Fix Version/s: 5.4.0.Final
(was: 5.4.0.Beta1)
(was: 5.3.1.Final)
Resolution: Done
NPE on modify when using lock-on-active after assert
----------------------------------------------------
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: Mark Proctor
Priority: Critical
Fix For: 5.4.0.Final
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
4430
days inactive
4612
days old
24 comments
12 participants
participants (12)
-
Cyril Sochor (JIRA) -
Edson Tirelli (Assigned) (JIRA)
-
Edson Tirelli (Closed) (JIRA)
-
Edson Tirelli (Resolved) (JIRA)
-
Edson Tirelli (Updated) (JIRA)
-
Emanuele Mariani (JIRA)
-
Jamie Shaw (Commented) (JIRA)
-
Jamie Shaw (Created) (JIRA)
-
Jamie Shaw (JIRA)
-
Jamie Shaw (Updated) (JIRA)
-
Mark Proctor (JIRA)
-
RH Bugzilla Integration (JIRA)