Jobs may not run properly on the Job Server

Overview

If a problem occurs in the TAC database, it is possible that Jobs will not run properly. This generally happens when there is a duplicate entry in the database that prevents normal operation. This could occur with manual execution or a scheduled job.

 

Environment

Windows or Linux

 

Symptoms/Description

Jobs from Job Conductor will not run either manually or on schedule.

The following error is located in the logs:

ERROR ExecutionTriggerableHelper  - org.talend.administrator.common.exception.UnicityExceptionorg.talend.administrator.common.exception.SystemException: org.talend.administrator.common.exception.UnicityException
        at org.talend.administrator.scheduler.persistence.helper.ExecutionTaskHelper.findByIdQuartzJob(ExecutionTaskHelper.java:495)
        at org.talend.administrator.scheduler.persistence.helper.ExecutionTaskHelper.findByIdQuartzJob(ExecutionTaskHelper.java:465)
  
        at org.talend.administrator.executionplan.persistence.helper.ExecutionTriggerableHelper.getByIdQuartzJob(ExecutionTriggerableHelper.java:99)
        at org.talend.administrator.scheduler.jobs.RemoteExecutionSwitcher.execute(RemoteExecutionSwitcher.java:44)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:199)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)
Caused by: org.talend.administrator.common.exception.UnicityException
        at org.talend.administrator.scheduler.persistence.helper.ExecutionTaskHelper.findByIdQuartzJob(ExecutionTaskHelper.java:490)
        ... 5 more

 

Resolution

To fix this issue, look at the ExecutionTask table in the TAC database.

Look for the same idQuartzJob duplicated in this table and remove the conflicting entry.

Note: Be sure you have a complete backup of the database before making any modifications to it.

Version History
Revision #:
8 of 8
Last update:
‎05-06-2017 01:25 AM
Updated by:
 
Tags (1)