Hide Forgot
DroolsEventProcessor contains knowledge session caching. Every ruleName has associated knowledgesession stored in a static map cache and the knowledgesession is primed with EPContext associated with the node. There are two bugs then 1) If there are two nodes with the same ruleName then the session is shared among them - effectively using wrong EPContext in one case 2) When the app is re-deployed then the session for no longer existing node is reused with invalid EPContext. Moreover Drools will stop evaluation of rules.
Removed static cache of sessions, as not really required, so now each distinct node has its own session.
Gary Brown <gary> updated the status of jira RTGOV-259 to Resolved
Gary Brown <gary> made a comment on jira RTGOV-259 Removed static cache of sessions, so now each node has its own session linked to its own EPNContext. Only issue is where the EPN (and therefore node) is updated to a new version - if temporal rules are used, then there is potential for some temporal dependencies to be lost by the correlated events spanning across the EPN versions.
Verified in ER4
Gary Brown <gary> updated the status of jira RTGOV-259 to Closed