Hi,
your last test case evidenced that there was something not covered by my fix
of DROOLS-516.
I resolved this issue with this further commit:
https://github.com/droolsjbpm/drools/commit/a833097b4
Thanks a lot for having reported this and regards,
Mario
--
View this message in context:
Ack'd and queued.
On 07/22/2014 11:46 PM, Kent Anderson wrote:
It appears there is another condition where Drools holds onto memory
indefinitely. (See https://issues.jboss.org/browse/DROOLS-516)
Use case: We have a set of rules designed to detect a heartbeat, then
report when/if the
