[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3075:
--------------------------------------------------
Edson Tirelli <etirelli(a)redhat.com> changed the Status of [bug
787118|https://bugzilla.redhat.com/show_bug.cgi?id=787118] from ASSIGNED to MODIFIED
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL:
https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
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