We do run about 75,000 to 90,000 processes per day and the majority of them are depending on the job executor.

How can we configure the thread pool to increase the number of threads in a non-Spring environment ?

We are configuring Activiti programmatically as follows:


ProcessEngineConfiguration processEngineConfiguration = ProcessEngineConfiguration.createStandaloneProcessEngineConfiguration();
processEngineConfiguration.setIdBlockSize(10000);
processEngineConfiguration.setDataSourceJndiName("jdbc/activitiPooledDS");
processEngineConfiguration.setTransactionsExternallyManaged(true);
processEngineConfiguration.setJobExecutorActivate(true);
processEngineConfiguration.setHistory(ProcessEngineConfiguration.HISTORY_ACTIVITY);
processEngineConfiguration.setDatabaseSchemaUpdate(ProcessEngineConfiguration.DB_SCHEMA_UPDATE_TRUE);

processEngine = processEngineConfiguration.buildProcessEngine();

Any help would be highly appreciated.

TIA
Joerg
WOW, that was fast smilie

Thanks a lot Tijs
Joerg
Thanks for your quick response.

Would you mind giving me an example ?

Thanks and best regards
Joerg
Hi,

I'm having a problem with timer boundary events being used in sub process loops.

My sub process is configured to loop subsequently and the first task actually is a receive task where a timer boundary event is being attached to, basically to function as a timeout - so if after a given period of time the receive task hasn't been triggered yet, the sub process will proceed upon the timeout - this is to avoid the sub process hanging endlessly. Another requirement is that the timeout time needs to be configurable and this is calculated within the last task of the sub process.

This all works fine on the very first iteration of the loop, but on all subsequent iterations the receive task doesn't wait to be triggered nor does it wait for the timeout, it just proceeds to the next task right away.

Any idea of what could be the cause for this problem ?

Thanks
Joerg