KieSession.scan() has inconsistent behaviour in BRMS 6.1

Solution In Progress - Updated -

Issue

When you use KieScanner.scanNow() to load an updated kjar, after updating, the rules are not firing as expected. The server has to be restarted and then the rules are firing as expected.

Given a simple project which contains some rules (a DRL file for each rule). If you deploy the project and run a test which fires those rules, it works fine. If you add a new rule, build and deploy and run the test after executing KieScanner.scanNow(), the new rule is fired as well. If you modify one of the rules so that it won't be matched, build and deploy and run again, then only the one rule will match and fire.

However, if you have one rule that matches, then modify this rule so that it won't match, and also add a new rule which will match, build and deploy and run the test after executing Kiescanner.scanNow(), then the modified one won't be matched but the new rule will not be fired.

If you restart the server, rules are firing as expected.

Environment

  • Red Hat JBoss BRMS
    • 6.1.0

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.