[
https://issues.jboss.org/browse/RTGOV-259?page=com.atlassian.jira.plugin....
]
Gary Brown resolved RTGOV-259.
------------------------------
Resolution: Done
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.
DroolsEventProcessor session caching not isolated or protected from
redeployments
---------------------------------------------------------------------------------
Key: RTGOV-259
URL:
https://issues.jboss.org/browse/RTGOV-259
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1.0.Final
Drools sessions are cached based on rule names, which are not necessarily unique across
EPNs.
When the drools event processor is initialised, it is associated with an EPNContext.
However if it already exists, this is not done. Therefore the issue is when a new version
of an EPN is deployed, the rule will remain associated with the original EPNContext.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira