There are options to restrict the size of the JVM memory allocation pool.
Loops can go over two or more rules, so take care. Catching such loops
is possible, up to a limit.
On 08/05/2014, kurrent93 <kurrent93(a)gmail.com> wrote:
We have an application where users write their own rules via a UI, and
are then translated into drl, and run in a dedicated drools session. Each
user can have one or more sessions.
However, there are times when something goes wrong - say a rule starts
looping - and it consumes all the resources - the server is running at 100%
cpu, and it then effects all users.
I realize we can optimize the the generated rules to prevent such issues,
and we are working on this - however am interested to know if there are any
ways - such as somehow sandboxing / restricting the resources that a drools
session can use, so that should a rule cause problems, it will not effect
the other running drools sessions.
Thanks for any advice on this problem.
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com
rules-users mailing list