AnsweredAssumed Answered

Jobexecutor tuning

Question asked by sazzadul on Aug 29, 2012
Latest reply on Sep 5, 2012 by trademak

     We are currently running activiti(version 5.10) in production with 3 instances of jobexecutor and with following configuration, database is oracle but the jobexecutor is not scaling upto our needs.
We have to create thousands of process instancess per hour.

<bean id="myJobExecutor" class="org.activiti.engine.impl.jobexecutor.DefaultJobExecutor">
      <property name="queueSize" value="30" />
      <property name="corePoolSize" value="30" />
      <property name="maxPoolSize" value="100" />
      <property name="maxJobsPerAcquisition" value="30" />
      <property name="waitTimeInMillis" value="1000" />
         <property name="lockTimeInMillis" value="180000"/>

   <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
         <property name="dataSource" ref="dataSource" />
         <property name="transactionManager" ref="transactionManager" />
         <property name="databaseSchemaUpdate" value="true" />
         <property name="jobExecutorActivate" value="true" />
         <property name="jobExecutor" ref="myJobExecutor" />
        <property name="history" value="activity" />
        <property name="idGenerator">
         <bean class="org.activiti.engine.impl.persistence.StrongUuidGenerator" />
        <property name="idBlockSize" value="2000" />

I am not seeing anything abnormal in the output log neither any memory usage issue. Is the configuration good enough ? Is there anything to tune in the database side like for instance adding indexes ?

It looks like jobexecutor suddenly becomes very slow.

Any help will be greatly appriciated