If you can set a limit for activations following one insert, an AgendaEventListener registering Before/AfterMatchFired is the natural choice. You might also limit secondary insertions (WorkingMemoryEventListener: ObjectInsertedEvent) or fact updates (ObjectUpdatedEvent).
All of this is highly dependent on the scenarios enacted by the rule set. -W On 08/05/2014, kurrent93 <[email protected]> wrote: > I was thinking of having a master session that can listen to activation > events of the child sessions, and then can take action should a threshold > be > breached. > > Can you recommend what eventlisteners would be useful in this scenario? > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Restrict-size-resource-usage-of-drools-session-tp4029486p4029488.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
