Hide Forgot
Date of First Response: 2010-02-01 14:20:48 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/460493 securitylevel_name: Public In a situations where multiple BRMS versions are deployed in HA environment the current KnowledgeAgent API is not capable to scan multiple locations for rule resources. KnowledgeAgent API should be able to scan multiple locations for the same resource or number of resources and be able to determine which location holds the "latest" version and pick that one up. Also, If one of the BRMS instances goes down, KnowledgeAgent API should be able to switch to receive resource updates only from the BRMS instance that is still up.
... and if no BRMS is up for a while, then use the local cache, until a BRMS is up again - then it should switch to it automatically and refresh the local cache.
I think agents following multiple sources is rather complicated. What does it happen if the BRMS instance that is up does not have the latest package version? Instead of it, it would be better that all BRMS instances are aware they are clusterized. When a user builds a new version of a package, the BRMS should send messages to all the other BRMS instances asking to update that package. The fail over between BRMS instances could be provided by any well known HA alternative (like mod_jk).
Part of this was implemented through https://jira.jboss.org/browse/JBRULES-2219. I am not sure if rest of the request is still needed but there should be a corresponding Guvnor or JBRules Jira for it first.
Link: Added: This issue depends JBRULES-2690
Link: Added: This issue depends JBRULES-2219
JBRULES-2219 / BRMS-348 resolve this issue as well.