[JBoss JIRA] Created: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
11:40 a.m.
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
3:37 p.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://jira.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plugin...
]
Will Lauer commented on JBRULES-2729:
-------------------------------------
I'm not sure I really understand the subtleties of the code yet, but it looks like the
solution for this is probably pretty simple. Instead of
CompositeMaxDurationTimer.createTrigger being defined as
public Trigger createTrigger(long timestamp,
String[] calendarNames,
Calendars calendars) {
return new CompositeMaxDurationTrigger( new Date( getMaxDuration() + timestamp ),
timer.createTrigger( timestamp,
calendarNames,
calendars ),
calendarNames,
calendars );
}
it should be instead modified, replacing the timer.createTrigger(...) with null, giving
public Trigger createTrigger(long timestamp,
String[] calendarNames,
Calendars calendars) {
return new CompositeMaxDurationTrigger( new Date( getMaxDuration() + timestamp ),
null,
calendarNames,
calendars );
}
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
1:29 a.m.
New subject: [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
5:32 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://issues.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plug...
]
Jacek Rosik commented on JBRULES-2729:
--------------------------------------
I'm experiencing the same problem. Any progress on it?
Adding 'duration' rule attribute resolves the problem with the NPE, but, the rule
is fired twice now. Once immediately and the after the specified time.
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://issues.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://issues.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plug...
]
Jacek Rosik edited comment on JBRULES-2729 at 12/20/10 6:31 AM:
----------------------------------------------------------------
I'm experiencing the same problem. Any progress on it?
Adding 'duration' rule attribute resolves the problem with the NPE, but, the rule
is fired twice now. Once immediately after conditions are satisfied, and then again after
the specified time.
was (Author: jrosik):
I'm experiencing the same problem. Any progress on it?
Adding 'duration' rule attribute resolves the problem with the NPE, but, the rule
is fired twice now. Once immediately and the after the specified time.
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://issues.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:06 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://issues.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plug...
]
Armin Steudte commented on JBRULES-2729:
----------------------------------------
Looks like this issue is equivalent with the one I'm experiencing.
Here the link https://issues.jboss.org/browse/JBRULES-2957
Progress would be very appreciated.
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://issues.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] Assigned: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://issues.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plug...
]
Edson Tirelli reassigned JBRULES-2729:
--------------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://issues.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: Edson Tirelli
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://issues.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plug...
]
Edson Tirelli updated JBRULES-2729:
-----------------------------------
Priority: Critical (was: Major)
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://issues.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: Edson Tirelli
Priority: Critical
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 p.m.
New subject: [JBoss JIRA] Resolved: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://issues.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plug...
]
Edson Tirelli resolved JBRULES-2729.
------------------------------------
Fix Version/s: 5.2.0.CR1
Resolution: Done
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://issues.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: Edson Tirelli
Priority: Critical
Fix For: 5.2.0.CR1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 p.m.
New subject: [JBoss JIRA] Closed: (JBRULES-2729) NullPointerException from CompositeMaxDurationTimer.createTrigger
[
https://issues.jboss.org/browse/JBRULES-2729?page=com.atlassian.jira.plug...
]
Edson Tirelli closed JBRULES-2729.
----------------------------------
NullPointerException from CompositeMaxDurationTimer.createTrigger
-----------------------------------------------------------------
Key: JBRULES-2729
URL: https://issues.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: Edson Tirelli
Priority: Critical
Fix For: 5.2.0.CR1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4891
days inactive
5109
days old
9 comments
5 participants
participants (5)
-
Armin Steudte (JIRA) -
Edson Tirelli (JIRA)
-
Jacek Rosik (JIRA)
-
Will Lauer (JIRA)
-
Wolfgang Laun (JIRA)