Updated rules in Guvnor do not get picked up in application code until restart

Solution Unverified - Updated -

Issue

  • The issue is faced with BRMS 5 where some of the rules set are firing in the application code according to their matched conditions in LHS of the rules. But it is noticed that not all the rules eligible to meet the condition is getting fired after those rules are updated in Guvnor and the desired output from the rule execution is not visible in the client code executing those rules as expected. e.g. if 2 order facts are placed in ksession, then the rules conditions which are suppose to match these 2 order facts are not firing and the application code is not showing the output.
  • Users are planning to move to BRMS 6 but this issue seems to be frequent with BRMS 5 whenever an update is made to the rules in Guvnor. The working memory is not functioning as expected and shows such behavior. The update made in the rules is not reflecting in working memory and hence the recent changes are not reflecting in client application code who run those rules against the facts. How to debug this kind of issue?
  • The firing of the updated rule is not always working properly/same way it is expected to work. Although this issue is not tested in BRMS 6 , but it is suspected to have happened because of the Knowledgebase not refreshing every-time an update is made to the rules and those updated rules are not being picked up by application code. Normally a server restart fixes these kind of issues if a rule is updated. Is there a permanent solution for this issue?

Environment

  • Red Hat JBoss BRMS (BRMS)
    • 5.3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.