Environment This article applies to users of Talend Administration Center. Symptoms/Description When many executions are pending for a Job on the Job Conductor page of Talend Administration Center, the status of your execution task might be frozen and the Refresh button might not be available. To solve this issue, you need to add a parameter to a configuration file. This parameter can be added to avoid the Job Conductor and Execution Plan pages from being blocked when retrieving the task's(or plan's) execution status of a huge number of scheduled executions. Resolution Stop Tomcat. Open the following file: \webapps\org.talend.administrator\WEB-INF\classes\configuration.properties Edit it as follows: scheduler.conf.retrieveExecStatus.timeout=30 to add a 30 seconds timeout to the execution status configuration. Note that the default value of the parameter is 0, which means that the timeout is disabled by default. Restart Tomcat. Next time you have many executions pending, a timeout message will be displayed in the web application and the user will be given the possibility to clear all executions.
When trying to export a profiling report that is generated with a user-defined JRXML template, all JRXML templates in the DQ repository of the studio are selected by default in the export wizard - and not only the template used by the report.
This exception happens when launching a workflow from Talend MDM. Talend MDM leverages the mdm_context variable to serialise and pass the model and entity data to the workflow engine embedded in Talend MDM.
This article details one possible cause for a Job to fail building and provides the corresponding solution. A number of reasons can cause a job building to fail. In this article, only the JDK installation and setting related error is detailed.