Jobs Not Running on Job Server with ExecutionTriggerableHelper error

Overview

If there is a duplicate entry in the TAC database that prevents normal operation, it is possible for Jobs to not run properly. This will occur with manual or scheduled job runs.


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 ExecutionTasktable in the TAC database. Look for the same idQuartzJob duplicated in the 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 #:
2 of 2
Last update:
‎06-16-2017 02:35 PM
Updated by:
 
Labels (1)
Tags (1)