Exception: 1 awaiting execution

Overview

Explains the error message and suggests a solution.

1 awaiting execution

 

Symptoms

The error occurs when trying to run a Job in Job Conductor, and you cannot stop the Job by killing it. This error is usually caused by many concurrent Job executions.

 

Procedure

To prevent this problem, follow these steps to increase the threadCount property in the quartz.properties file to always be greater than the max running time of the concurrent tasks:

  1. Go to the Tomcat_install_dir/webapps/org.talend.administrator/WEB_LIB/conf/class/ directory and open the quartz.properties file.

  2. Search for threadCount and increase its value.

    The default setting is:

    org.quartz.threadPool.threadCount = 20

    So for example, for 30 max concurrent executions, you can set:

    org.quartz.threadPool.threadCount = 30
  3. Save the file and restart Tomcat.

Version history
Revision #:
2 of 2
Last update:
‎06-21-2017 08:17 PM
Updated by:
 
Labels (1)
Tags (1)
Comments
njoychan

Hi, I found a salesforce article https://na33.salesforce.com/kA039000000CpV9?srPos=4&srKp=ka0&lang=en_US based on which it is a good idea to optimise the following parameters  along with thread count.

 

hibernate.c3p0.max_size (set in the configuration.properties file)
org.quartz.dataSource.QRTZ_DS.maxConnections (set in the quartz.properties file)

 

It also has the following note:

 

It is important that the hibernate.c3p0.max_size > org.quartz.dataSource.QRTZ_DS.maxConnections

You will need to restart the Tomcat / TAC for the change to take effect.

 

This particular situation was occuring as the hibernate.c3p0.max_size <  org.quartz.dataSource.QRTZ_DS.maxConnections

After changing the values, TAC was behaving well and stopped crashing.