[
https://issues.jboss.org/browse/DROOLS-1247?page=com.atlassian.jira.plugi...
]
Mario Fusco commented on DROOLS-1247:
-------------------------------------
Partially fixed by
https://github.com/droolsjbpm/drools/commit/45fb1d622759d3f439b9a089fa1b5...
There is still one unresolved test failure that needs to be investigated and fixed
https://github.com/droolsjbpm/drools/commit/45fb1d622759d3f439b9a089fa1b5...
The NPE in that test is caused by the fact that the same NotNode is evaluated twice during
the same flushing operation and the second time there is a staged child left tuple that it
tries to remove. The problem is that the node is not the tip of the segment so there
isn't actually any staged list to be cleared and the NPE is thrown when the node tries
to do so. The other interesting fact is that the path is already totally linked during
that evaluation so it would also important to figure out why the same test doesn't
fail in lazy mode.
ForceEagerActivationOption may cause a recursive segment
initialization
-----------------------------------------------------------------------
Key: DROOLS-1247
URL:
https://issues.jboss.org/browse/DROOLS-1247
Project: Drools
Issue Type: Bug
Components: core engine
Reporter: Mario Fusco
Assignee: Mario Fusco
Priority: Blocker
ForceEagerActivationOption may cause a recursive segments initialization resulting in an
infinite recursive linked list of segment memories like: smem1 -> smem2 -> smem1
-> ... When this happens the segments evaluation makes the engine to fall in an endless
loop.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)