Job Executor stop polling jobs after a while

[d200...@yahoo.com]

Hi,

i have deployed a camunda BPM Platform on a Tomcat Server. On this platform, i have configured a process engine and its job executor. I have created a process definition which contains a service task, 2 exclusive gateways and a timer-event. I have marked the service task as asynchronous-after. My goal is to keep process instance of this process definition live forever unless i explicit cancel it. So far so good, the job executor worked perfectly for a while and then stopped picking up job in the table act_ru_job. Do you have any ideas why the job-executor stopped picking up job? Or do i have to do some special configuration for the job-executor in the bpm-platform.xml file? Below is my configuration for job-executor.

<job-executor>
<job-acquisition name="default">
<properties>
<property name="maxJobsPerAcquisition">50</property>
<property name="waitTimeInMillis">8000</property>
<property name="lockTimeInMillis">400000</property>
</properties>
</job-acquisition>
<properties>
<property name="queueSize">30</property>
<property name="corePoolSize">10</property>
<property name="maxPoolSize">50</property>
<property name="keepAliveTime">5000</property>
</properties>
</job-executor>

<process-engine name="default">
<job-acquisition>default</job-acquisition>
<configuration>org.camunda.bpm.engine.impl.cfg.StandaloneProcessEngineConfiguration</configuration>
<datasource>java:jdbc/ProcessEngine</datasource>
<properties>
<property name="history">full</property>
<property name="databaseSchemaUpdate">true</property>
<property name="authorizationEnabled">true</property>
<property name="jobExecutorActivate">true</property>
<property name="jobExecutorDeploymentAware">true</property>
<property name="defaultNumberOfRetries">1</property>
</properties>
Thanks you all in advance.

Best Regard,

Nam

[thorben....@camunda.com]

Hi Nam,

Which Camunda version do you use? Can you please post the contents of ACT_RU_JOB for the jobs that belong to the process instance in question?

Cheers,
Thorben

[d200...@yahoo.com]

Hi Thorben,

thanks for your prompt reply. I'm using 7.4.0-alpha2. Below is the contents of ACT_RU_JOB right now. As you can see, duedate is in the past (2016-02-29 16:30:07.489) but my job-executor stopped picking up job.

{| border="1"
! <nowiki>ID_</nowiki>
! <nowiki>REV_</nowiki>
! <nowiki>TYPE_</nowiki>
! <nowiki>LOCK_EXP_TIME_</nowiki>
! <nowiki>LOCK_OWNER_</nowiki>
! <nowiki>EXCLUSIVE_</nowiki>
! <nowiki>EXECUTION_ID_</nowiki>
! <nowiki>PROCESS_INSTANCE_ID_</nowiki>
! <nowiki>PROCESS_DEF_ID_</nowiki>
! <nowiki>PROCESS_DEF_KEY_</nowiki>
! <nowiki>RETRIES_</nowiki>
! <nowiki>EXCEPTION_STACK_ID_</nowiki>
! <nowiki>EXCEPTION_MSG_</nowiki>
! <nowiki>DUEDATE_</nowiki>
! <nowiki>REPEAT_</nowiki>
! <nowiki>HANDLER_TYPE_</nowiki>
! <nowiki>HANDLER_CFG_</nowiki>
! <nowiki>DEPLOYMENT_ID_</nowiki>
! <nowiki>SUSPENSION_STATE_</nowiki>
! <nowiki>JOB_DEF_ID_</nowiki>
! <nowiki>PRIORITY_</nowiki>
! <nowiki>SEQUENCE_COUNTER_</nowiki>
|-
| <nowiki>470c9d13-def9-11e5-9772-005056800def</nowiki>
| <nowiki>12</nowiki>
| <nowiki>timer</nowiki>
| <nowiki>2016-02-29 17:43:29.752</nowiki>
| <nowiki>6ccb4fbf-c56d-4d63-bda8-6e416cc9dafc</nowiki>
| <nowiki>1</nowiki>
| <nowiki>470c4ef1-def9-11e5-9772-005056800def</nowiki>
| <nowiki>28d6bdca-deef-11e5-b149-005056800def</nowiki>
| <nowiki>masterprocess:4:d3d6fba8-d3f8-11e5-ba77-005056800def</nowiki>
| <nowiki>masterprocess</nowiki>
| <nowiki>1</nowiki>
| <nowiki><null></nowiki>
| <nowiki><null></nowiki>
| <nowiki>2016-02-29 16:30:07.489</nowiki>
| <nowiki><null></nowiki>
| <nowiki>timer-intermediate-transition</nowiki>
| <nowiki>IntermediateCatchEvent_2</nowiki>
| <nowiki>d3b0fdff-d3f8-11e5-ba77-005056800def</nowiki>
| <nowiki>1</nowiki>
| <nowiki>d3d6fbae-d3f8-11e5-ba77-005056800def</nowiki>
| <nowiki>0</nowiki>
| <nowiki>1</nowiki>
|-
| <nowiki>ec8c5d37-deef-11e5-8a79-005056800def</nowiki>
| <nowiki>21</nowiki>
| <nowiki>message</nowiki>
| <nowiki>2016-02-29 17:43:13.743</nowiki>
| <nowiki>6ccb4fbf-c56d-4d63-bda8-6e416cc9dafc</nowiki>
| <nowiki>1</nowiki>
| <nowiki>fd62a052-deee-11e5-b149-005056800def</nowiki>
| <nowiki>fd62a052-deee-11e5-b149-005056800def</nowiki>
| <nowiki>workflow_queue_verwalten:4:d3d749d0-d3f8-11e5-ba77-005056800def</nowiki>
| <nowiki>workflow_queue_verwalten</nowiki>
| <nowiki>1</nowiki>
| <nowiki><null></nowiki>
| <nowiki><null></nowiki>
| <nowiki><null></nowiki>
| <nowiki><null></nowiki>
| <nowiki>async-continuation</nowiki>
| <nowiki>transition-create-scope</nowiki>
| <nowiki>d3b0fdff-d3f8-11e5-ba77-005056800def</nowiki>
| <nowiki>1</nowiki>
| <nowiki>d3d749d2-d3f8-11e5-ba77-005056800def</nowiki>
| <nowiki>0</nowiki>
| <nowiki>1</nowiki>

[thorben....@camunda.com]

Hi Nam,

You could set the log level for the following packages to FINEST to get an idea what is going on:

org.camunda.bpm.engine.impl.persistence.entity.JobEntity.selectNextJobsToExecute
org.camunda.bpm.engine.impl.jobexecutor.SequentialJobAcquisitionRunnable
org.camunda.bpm.engine.impl.jobexecutor.AcquireJobsRunnable

Cheers,
Thorben

[d200...@yahoo.com]

Hi Thorben,

thanks for your prompt reply, i maybe ask a noob question, but how can i set the log level for these packages? in the pom.xml or in the bpm-platform.xml file? Thank you in advance.

Cheers,

Nam

[thorben....@camunda.com]

Hi Nam,

You can find some general documentation on logging in Camunda at [1]. When using a shared engine, logging configuration is typically in a central, server-specific place. Which server do you use?

Cheers,
Thorben

[1] https://docs.camunda.org/manual/latest/user-guide/logging/

Cheers,
Thorben

[d200...@yahoo.com]

Hi Thorben,

thanks for your always prompt reply. I'm using slf4j and logback. Now i know where i can set the log level.

Cheers,

Nam