Hi Michael, You can control the maximum number of threads in Ode by setting the " ode-jbi.threads.pool.size" parameter in your ode-jbi.properties file (you might have to create it if it doesn't exist)
ode-jbi.threads.pool.size=50 With ServiceMix this file must reside under $SERVICEMIX_HOME/data/smx/components/OdeBpelEngine/version_XX/ode- jbi.properties Unfortunately, there's a bug in Ode 1.0 whereby the parameter is ignored. If you want to use this parameter, you'll have to use the development trunk (which is quite stable nowadays). cheers, alex On 6/27/07, Michael Horwitz <[EMAIL PROTECTED]> wrote:
Hi, I am running ODE 1.0 under ServiceMix and am rapidly running out of memory if there is a sudden surge in messages to the Ode component invoking new process instances. I am running a single process in memory. It appears (although I may well be wrong) that Ode reads the message off the bus and spawns one or more new thread(s) for each process invocation. Is there a way to limit the number of threads spawned by Ode? i.e. let the queues in ServiceMix absorb the message spurt. I have tried limiting the Seda queue thread pool size, but it seems to have no effect - Ode is just too good at getting the messages off the queue! Thanks Mike.
