[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://jira.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plugin...
]
Wolfgang Laun commented on JBRULES-2729:
----------------------------------------
A similar rule where the NPE occurs in the line before:
at
org.drools.time.impl.CompositeMaxDurationTimer.createTrigger(CompositeMaxDurationTimer.java:58)
is this:
rule "match-start-end"
when
$start: CallStart( $s: source, $d: destination, $st: time )
not CallStart( this before $start )
### !!! ###
$end: CallEnd( source == $s, destination == $d, $et: time )
not CallEnd( source == $s, destination == $d, this before $end ) ### !!! ###
then
//...
end
Omitting ONE of the marked "not" CEs avoids the NPE.
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://jira.jboss.org/browse/JBRULES-2729
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler
Affects Versions: 5.1.1.FINAL
Environment: Windows XP SP3, Java 1.6.0_21, Drools Fusion 5.1.1
Reporter: Will Lauer
Assignee: Mark Proctor
The timer field of CompositeMaxDurationTimer appears to be not getting populated
correctly when certain types of rules are created in Drools Fusion. This results in
subsequent calls to CompositeMaxDurationTimer.createTimer to reference a null pointer
during execution. While the error triggers during fact insertion in Drools Fusion, it
appears to be due to an incomplete timer definition during rules compilation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira