Skip to Content
Sep 18, 2014 at 01:44 PM

Max concurrent RT engines is ignored


Dear experts,

my use case is to execute initial load jobs for a large number of backend systems in an automated fashion without any resource contention.

I've configured an IdM 7.2 SP7 system with one dispatcher to start at most two concurrent runtime engines. This is configured both as a global setting and on the single dispatcher (see screenshots).

Then I execute a normal job with one toGeneric pass whose entry script uses uRunJobNow() to start the ~50 initial load jobs. My expectation was that these jobs would now be executed in sequence, with at most two jobs running in parallel.

Unfortunately, that's not the case. In fact, up to 16 runtimes are started in parallel, so resource contention occurs with the usual problems (OutOfMemory, timeout etc.). The dispatcher log emits warning messages:

Not allowed to start ANY runtimes (right now running runtimes = 16, allowed total runtimes = 2

Question: is there anything I need to change in the dispatcher configuration to achieve the desired behavior?

Best regards,