I tried a sample example to see how agenda-group works. Initially I set the focus of ksession to agenda-group \"ag1\" and fired the rules.
package com.sample
im
Agenda groups work like a stack. When you set the focus to a given agenda group, that group is placed on top of the stack. When the engine tries to fire the next activation and there are no more activations in a given group, that group is removed from the top of the stack and the group below it receives the focus again.
So it goes like this (main is the default group that is always present):
* STACK: [MAIN, ag1]
Hello Word fires and activates both "GoodBye" rules
GoodBye fires, activates both "Hello World" rules and sets the focus to "ag2"
* STACK: [MAIN, ag1, ag2]
Hellow World 2 fires, cancels the "Hello World 1" rule and activates both "GoodBye" rules
GoodBye 2 fires because ag2 has the focus
* There are no more activations in ag2 to fire, so ag2 is removed from the stack
* STACK: [MAIN, ag1]
* The "GoodBye" rule is still active in ag1, so it fires
GoodBye fires, activates both "Hello World" rules and sets the focus to "ag2"
* STACK: [MAIN, ag1, ag2]
Hellow World 2 fires, cancels the "Hello World 1" rule and activates both "GoodBye" rules
...
And the loop repeats.
This kind of behavior is very easy to see if you use the audit log in the Eclipse IDE.
Hope this helps.
Since you changed facts in the session (your Message object is in your facts i guess) during the computation of a rule, other rules are computed again, not depending on the agenda-group they belong to, in order to update the Drools knowledge base.
You could add no-loop true
to prevent this on the line after rule
definition
I'm not quiet sure, but it's the behavior i noticed on my app and should so resolve your infinite loop. By the way, it seems logical to compute again rules when facts change.