[resolved] TAC generation error from downloaded component.

Anonymous — Sat, 16 Nov 2024 11:30:21 GMT

Hi,
I've been using the PLSAPSimpleInput () component in a job on my development server, and when loaded and used, everything was fine. Yesterday I began migrating jobs to the production environment, which is hosted on a new server. After copying the jobs into a new project and setting up a new TAC, this job will not generate, though it runs correctly in studio with a Target Exec on the TAC server machine.
When I attempted to generate the job, this error was given:
java.lang.RuntimeException: org.talend.commons.exception.PersistenceException: Process cannot be opened because a used component <org.talend.designer.core.model.utils.emf.talendfile.impl.NodeTypeImpl@7ac511f1 (binaryData: null, stringData: null, componentName: tPLSAPSimpleInput, componentVersion: 0.101, offsetLabelX: 0, offsetLabelY: 0, posX: 256, posY: 96, sizeX: 32, sizeY: 35, screenshot: null)> is not loaded
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:148)
at org.talend.commandline.client.command.extension.AbstractExtensionCommandSwitch.doSwitch(AbstractExtensionCommandSwitch.java:31)
at org.talend.commandline.command.CommandProcessorSwitch.caseExtensionCommand(CommandProcessorSwitch.java:161)
at org.talend.commandline.client.util.CommandAbstractSwitch.doSwitch(CommandAbstractSwitch.java:70)
at org.talend.commandline.command.CommandConsumer.executeCommand(CommandConsumer.java:57)
at org.talend.commandline.command.CommandConsumer.execute(CommandConsumer.java:35)
at org.talend.commandline.mode.ServerCommandLine$CommmandConsumerRunnable.run(ServerCommandLine.java:139)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.talend.commons.exception.PersistenceException: Process cannot be opened because a used component <org.talend.designer.core.model.utils.emf.talendfile.impl.NodeTypeImpl@7ac511f1 (binaryData: null, stringData: null, componentName: tPLSAPSimpleInput, componentVersion: 0.101, offsetLabelX: 0, offsetLabelY: 0, posX: 256, posY: 96, sizeX: 32, sizeY: 35, screenshot: null)> is not loaded
at org.talend.designer.core.ui.editor.process.Process.checkLoadNodes(Process.java:2098)
at org.talend.commandline.util.JobHandler.export(JobHandler.java:237)
at org.talend.commandline.command.execute.BuildJobExecuteCommand.execute(BuildJobExecuteCommand.java:93)
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:146)
... 7 more
org.talend.gwtadministrator.client.module.dashboard.commandline.model.CommandLineBean.executeGroupCommand(CommandLineBean.java:250)
org.talend.administrator.scheduler.business.job.generate.JobGenerator.executeGroupCommand(JobGenerator.java:308)
org.talend.administrator.scheduler.business.job.generate.JobGenerator.generate(JobGenerator.java:148)
org.talend.administrator.scheduler.business.ExecutionTaskHandler.generateJobScriptUnit(ExecutionTaskHandler.java:374)
org.talend.administrator.scheduler.business.ExecutionTaskHandler.runTaskUnit(ExecutionTaskHandler.java:918)
org.talend.administrator.scheduler.jobs.RemoteTaskExecution.executeRemoteJob(RemoteTaskExecution.java:351)
org.talend.administrator.scheduler.jobs.RemoteTaskExecution.execute(RemoteTaskExecution.java:192)
org.talend.administrator.scheduler.jobs.RemoteExecutionSwitcher.execute(RemoteExecutionSwitcher.java:50)
org.quartz.core.JobRunShell.run(JobRunShell.java:199)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)
Caused by: java.lang.RuntimeException: org.talend.commons.exception.PersistenceException: Process cannot be opened because a used component <org.talend.designer.core.model.utils.emf.talendfile.impl.NodeTypeImpl@7ac511f1 (binaryData: null, stringData: null, componentName: tPLSAPSimpleInput, componentVersion: 0.101, offsetLabelX: 0, offsetLabelY: 0, posX: 256, posY: 96, sizeX: 32, sizeY: 35, screenshot: null)> is not loaded
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:148)
at org.talend.commandline.client.command.extension.AbstractExtensionCommandSwitch.doSwitch(AbstractExtensionCommandSwitch.java:31)
at org.talend.commandline.command.CommandProcessorSwitch.caseExtensionCommand(CommandProcessorSwitch.java:161)
at org.talend.commandline.client.util.CommandAbstractSwitch.doSwitch(CommandAbstractSwitch.java:70)
at org.talend.commandline.command.CommandConsumer.executeCommand(CommandConsumer.java:57)
at org.talend.commandline.command.CommandConsumer.execute(CommandConsumer.java:35)
at org.talend.commandline.mode.ServerCommandLine$CommmandConsumerRunnable.run(ServerCommandLine.java:139)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.talend.commons.exception.PersistenceException: Process cannot be opened because a used component <org.talend.designer.core.model.utils.emf.talendfile.impl.NodeTypeImpl@7ac511f1 (binaryData: null, stringData: null, componentName: tPLSAPSimpleInput, componentVersion: 0.101, offsetLabelX: 0, offsetLabelY: 0, posX: 256, posY: 96, sizeX: 32, sizeY: 35, screenshot: null)> is not loaded
at org.talend.designer.core.ui.editor.process.Process.checkLoadNodes(Process.java:2098)
at org.talend.commandline.util.JobHandler.export(JobHandler.java:237)
at org.talend.commandline.command.execute.BuildJobExecuteCommand.execute(BuildJobExecuteCommand.java:93)
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:146)
... 7 more
At this point I've included the necessary files in the studio section of the TAC installation on the server, and can run it there, but still cannot generate it in TAC. Is there something I'm missing in regards to TAC + talend exchange components? I should also note that it is not stored in a custom component folder, but added into the plugins/lib/etc. folders as needed, so I don't have TAC connecting to a custom component folder in configuration settings (but this wasn't the case on the DEV server either).
Can anyone help?

Re: [resolved] TAC generation error from downloaded component.

Anonymous — Thu, 11 Sep 2014 20:46:43 GMT

You have to copy the components to the TAC server and point in the TAC -> Configuration-> Commandline in the attribute Custom Component Path to this directory.
You will see an effect if you build a task and see in the in the Commandline view the additional action setCustomComponentpath

topic [resolved] TAC generation error from downloaded component. in Talend Studio

[resolved] TAC generation error from downloaded component.

Re: [resolved] TAC generation error from downloaded component.