[jboss-jira] [JBoss JIRA] (JBRULES-3307) Event does not expire when temporal operators are used.

Event does not expire when temporal operators are used. ------------------------------------------------------- Key: JBRULES-3307 URL: https://issues.jboss.org/browse/JBRULES-3307 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Final Environment: OS: Windows XP Java: 1.6.0_29 Reporter: Scott Embler Assignee: Mark Proctor Expectations: When rules use temporal operators to relate two events in time, it is expected that those both events will be expired when the session clock advances far enough. In the unit tests I have provided you'll see that there are two event types A and B. Each rule tries to relate these two events using a different temporal operator. After the rules match, both A and B should be expired, and a String should be inserted into working memory to signal to the test that the rule worked. Observed behavior: When A and B are inserted into their respective entry points the rules do match, and the appropriate String is inserted into working memory. B is also retracted. However A remains in working memory forever, causing heap space exceptions if there are many A's to process. It can also be seen using JMX that the computed event expiration for B is 0, and for A is the maximum long value. -- 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