[
https://issues.jboss.org/browse/DROOLS-4393?page=com.atlassian.jira.plugi...
]
Kris Verlaenen updated DROOLS-4393:
-----------------------------------
Sprint: 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 29-31)
Expired events can be present in the collect result
---------------------------------------------------
Key: DROOLS-4393
URL:
https://issues.jboss.org/browse/DROOLS-4393
Project: Drools
Issue Type: Feature Request
Components: core engine
Affects Versions: 7.24.0.Final
Reporter: Alberto Fanjul Alonso
Assignee: Mario Fusco
Priority: Major
Attachments: reproducer-02425402.zip
Is there any option to expire the facts before fireAllRules()?
A reproducer for drools 6.5.0.Final-redhat-25 (tested too on 7.23.0.Final-redhat-00002
and 7.24.0.Final) shows that facts are not expired until we run fireAllRules().
Trying reproducer:
Show facts are expired after fireAllRules():
```
unzip -d reproducer reproducer-02425402.zip
cd reproducer
git checkout master
./run.sh
```
Show facts are not expired before fireAllRules():
```
git checkout original
./run.sh
```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)