[
https://jira.jboss.org/jira/browse/JBRULES-2201?page=com.atlassian.jira.p...
]
Kit Chan commented on JBRULES-2201:
-----------------------------------
I don't have a standalone sample right now, but what I figured out is when a
RuleFlowGroup node triggers an external event (from a rule in a drl file), and that event
will lead to an End node that ends the main process. Then with the next run of the process
(by inserting another fact), what happened is the RuleFlowGroup node that triggered the
external event in the last run is trying to execute again with the previous object, which
the object is removed from the working memory already, so it ends up with a Null Pointer
Exception. I called the dispose method at the end of every run, but seems like it
doesn't dispose everything the way it supposed to.
Rule got executed even does not satisfy LHS after firing an external
event in Flow
----------------------------------------------------------------------------------
Key: JBRULES-2201
URL:
https://jira.jboss.org/jira/browse/JBRULES-2201
Project: JBoss Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert), drools-core (flow)
Affects Versions: 5.0.1.FINAL
Environment: Windows XP SP3, Eclipse 3.4.2
Reporter: Kit Chan
Assignee: Kris Verlaenen
Priority: Critical
I am using Flow to create the workflow of the process and the rules are defined in a DRL
file. I have a rule that will trigger an external event defined in the Flow. So the
scenario is I will insert one fact in the Knowledge Session and start the process, once
the process is finished, it will insert anoother fact and start another process, keep
repeating this procedures for numbers of time. The problem is once an external event got
triggered once, it will cause the rule that trigger the external event everytime even the
condition that specified in the LHS of the rule doesn't match. And the fact is NULL
in those cases, I checked the activation plan, the rule is not activated but still got
executed somehow.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira