Lock-on-active was very recently the subject of a bad bug, DROOLS-281, which has been fixed a few days ago. This said, all rules that do not have an explicit group set end up in the "MAIN" (or "DEFAULT", I don't remember) agenda group and then behave accordingly. Could you post the Drools version number and some more details on the example and the "unexpected" behavior? Thanks Davide On 11/07/2013 03:01 PM, Stephen Masters wrote: > Hi folks, > > According to the user guide, lock-on-active “inhibits additional activations of all rules with this flag set within the same rule flow or agenda group”. > > I was doing a little testing of some rules earlier today, and noticed that lock-on-active seems to change behaviour when applied to rules which don’t have an agenda-group or rules flow-group defined. It also seemed to have a slightly inconsistent effect, although that may just be me not realising what it’s supposed to do. > > There doesn’t appear to be any documentation of what the attribute means when a rule is not part of a rule flow or agenda group. So I was wondering whether perhaps there is an expected/official behaviour, which is just not documented. Or is lock-on-active without a rule flow or agenda group an error? In which case is there a reason why it doesn’t cause a compilation error when the knowledge base is built? > > Yours curiously... > > Steve > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users