Error while generating job

Five Stars ami
Five Stars

Error while generating job

Dear All,

IN my DEV environment , i am unable to generate any jobs suddenly till yesterday it was all fine , those jobs which are error free thy are running fine , but  when i do generate on them it says error while generating .





Also see the Command line error :

[Cause by command 2134 => BuildJobServerCommand buildJob 'TEST' -dd '/opt/talend/CommandLine/exports/task_776' -af '1480907437879_task_776' -jc 'Default' -jall 'Info' -jv '0.1' -jt 'PROCESS' -jstats -il -ic -ijs -its -et -bin]

Also configuration section seems to be fine :-





Any help appreciated , its urgent .

Thanks.
Amit

Moderator

Re: Error while generating job

Hi,
Could you please indicate what's the build version you are using? Is your license valid for you?
 The DEV environment network is OK with you?
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars ami
Five Stars

Re: Error while generating job

Dear Sabrina,

Its talend 6.1
and licence will expire in 5 days time .
i am able to run the jobs but not able to generate it.

Thanks,
Amit
Five Stars ami
Five Stars

Re: Error while generating job

Dear sabrina,

I am able to ping the IP of dev environment , how to check the network?
Regards,
Amit
Moderator

Re: Error while generating job

Hi,
Is there any error message in your TAC log?
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars ami
Five Stars

Re: Error while generating job

Dear,

The log is below:-

java.lang.RuntimeException: org.talend.designer.runprocess.ProcessorException: java.lang.Exception: Job was not built successfully, please check the logs for more details
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:179)
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:745)
Caused by: org.talend.designer.runprocess.ProcessorException: java.lang.Exception: Job was not built successfully, please check the logs for more details
at org.talend.commandline.util.JobHandler.export(JobHandler.java:229)
at org.talend.commandline.command.execute.BuildJobExecuteCommand.execute(BuildJobExecuteCommand.java:143)
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:177)
... 7 more
Caused by: java.lang.Exception: Job was not built successfully, please check the logs for more details
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:229)
at org.talend.commandline.util.JobHandler.export(JobHandler.java:218)
... 9 more

org.talend.gwtadministrator.client.module.dashboard.commandline.model.CommandLineBean.executeGroupCommand(CommandLineBean.java:274)
org.talend.administrator.scheduler.business.job.generate.JobGenerator.executeGroupCommand(JobGenerator.java:311)
org.talend.administrator.scheduler.business.job.generate.JobGenerator.generate(JobGenerator.java:151)
org.talend.administrator.scheduler.business.ExecutionTaskHandler.generateJobScriptUnit(ExecutionTaskHandler.java:433)
org.talend.administrator.scheduler.business.ExecutionTaskHandler.runTaskUnit(ExecutionTaskHandler.java:1082)
org.talend.administrator.scheduler.jobs.RemoteTaskExecution.executeRemoteJob(RemoteTaskExecution.java:472)
org.talend.administrator.scheduler.jobs.RemoteTaskExecution.execute(RemoteTaskExecution.java:248)
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.designer.runprocess.ProcessorException: java.lang.Exception: Job was not built successfully, please check the logs for more details
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:179)
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:745)
Caused by: org.talend.designer.runprocess.ProcessorException: java.lang.Exception: Job was not built successfully, please check the logs for more details
at org.talend.commandline.util.JobHandler.export(JobHandler.java:229)
at org.talend.commandline.command.execute.BuildJobExecuteCommand.execute(BuildJobExecuteCommand.java:143)
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:177)
... 7 more

Caused by: java.lang.Exception: Job was not built successfully, please check the logs for more details
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:229)
at org.talend.commandline.util.JobHandler.export(JobHandler.java:218)
... 9 more


This is from the TAC job conductor. I am puzzeled as the job runs  on talend studio and  those jobs which are running fine , but when i do generated on the running jobs , it says error while generating.
Five Stars ami
Five Stars

Re: Error while generating job

Dear ,

Is there is any other way to track / check logs? if you do let me know , and i will share the log with you 
here the first line says , job was not generated , please see logs , now where to check this?

Regards
Amit
Moderator

Re: Error while generating job

Hi Amit,
Did you check the log located in {cmdline installation path}\studio\commandline-workspace\.metadata?
[font=Calibri, sans-serif]Have you tried to these steps to see if it works? Let us know if it is Ok with you.[/font]
1. Stop the commandline. 
2. Delete the commandline-workspace.
3. Restart commandline and generate the task again.
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars ami
Five Stars

Re: Error while generating job

Dear Sabrina,

I see two command lines configured 



Do i have to stopped both and delete the  commanline workspace?





Also from the .metadata this is the latest log:

!ENTRY org.talend.platform.logging 4 0 2016-12-04 22:21:14.343
!MESSAGE 2016-12-04 22:21:14,342 ERROR org.talend.commons.exception.CommonExceptionHandler  - Could not read pom.xml

!STACK 1
org.eclipse.core.runtime.CoreException: Could not read pom.xml
at org.eclipse.m2e.core.internal.embedder.MavenImpl.readModel(MavenImpl.java:558)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.readModel(MavenImpl.java:567)
at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenModel(MavenModelManager.java:99)
at org.talend.designer.maven.launch.MavenPomCommandLauncher.execute(MavenPomCommandLauncher.java:78)
at org.talend.designer.runprocess.java.TalendProcessJavaProject.mavenBuildCodeProjectPom(TalendProcessJavaProject.java:303)
at org.talend.designer.runprocess.java.TalendProcessJavaProject.buildModules(TalendProcessJavaProject.java:258)
at org.talend.repository.ui.wizards.exportjob.handler.BuildJobHandler.buildDelegate(BuildJobHandler.java:370)
at org.talend.repository.ui.wizards.exportjob.handler.BuildJobHandler$1.run(BuildJobHandler.java:347)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.talend.repository.ui.wizards.exportjob.handler.BuildJobHandler.build(BuildJobHandler.java:356)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager$1.run(BuildJobManager.java:182)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:196)
at org.talend.commandline.util.JobHandler.export(JobHandler.java:218)
at org.talend.commandline.command.execute.BuildJobExecuteCommand.execute(BuildJobExecuteCommand.java:143)
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:177)
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:745)
Caused by: java.io.EOFException: no more data available - expected end tags </dependency></dependencies></project> to close start tag <dependency> from line 349 and start tag <dependencies> from line 18 and start tag <project> from line 2, parser stopped on TEXT seen ...<version>6.0.0-SNAPSHOT</version>\n    </... @353:7
at org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3063)
at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3074)
at org.codehaus.plexus.util.xml.pull.MXParser.parseEndTag(MXParser.java:1698)
at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1169)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1131)
at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1118)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseDependency(MavenXpp3Reader.java:1312)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2197)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3807)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:557)
at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:122)
at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:91)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.readModel(MavenImpl.java:556)
... 22 more
!SUBENTRY 1 org.eclipse.m2e.core 4 -1 2016-12-04 22:21:14.343
!MESSAGE Could not read pom.xml
!STACK 0
java.io.EOFException: no more data available - expected end tags </dependency></dependencies></project> to close start tag <dependency> from line 349 and start tag <dependencies> from line 18 and start tag <project> from line 2, parser stopped on TEXT seen ...<version>6.0.0-SNAPSHOT</version>\n    </... @353:7
at org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3063)
at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3074)
at org.codehaus.plexus.util.xml.pull.MXParser.parseEndTag(MXParser.java:1698)
at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1169)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1131)
at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1118)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseDependency(MavenXpp3Reader.java:1312)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2197)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3807)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:557)
at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:122)
at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:91)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.readModel(MavenImpl.java:556)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.readModel(MavenImpl.java:567)
at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenModel(MavenModelManager.java:99)
at org.talend.designer.maven.launch.MavenPomCommandLauncher.execute(MavenPomCommandLauncher.java:78)
at org.talend.designer.runprocess.java.TalendProcessJavaProject.mavenBuildCodeProjectPom(TalendProcessJavaProject.java:303)
at org.talend.designer.runprocess.java.TalendProcessJavaProject.buildModules(TalendProcessJavaProject.java:258)
at org.talend.repository.ui.wizards.exportjob.handler.BuildJobHandler.buildDelegate(BuildJobHandler.java:370)
at org.talend.repository.ui.wizards.exportjob.handler.BuildJobHandler$1.run(BuildJobHandler.java:347)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.talend.repository.ui.wizards.exportjob.handler.BuildJobHandler.build(BuildJobHandler.java:356)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager$1.run(BuildJobManager.java:182)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:196)
at org.talend.commandline.util.JobHandler.export(JobHandler.java:218)
at org.talend.commandline.command.execute.BuildJobExecuteCommand.execute(BuildJobExecuteCommand.java:143)
at org.talend.commandline.command.ExtensionCommandSwitch.caseExtensionServerCommand(ExtensionCommandSwitch.java:177)
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:745)

Please suggest?

Regards
Amit
Moderator

Re: Error while generating job

Hi Amit,
Would you mind reporting a ticket on talend support portal for your current subscription product? In this way, we can give you a remote assistance(webex) on your issue through support cycle with priority.
Best regards
Sabrina 
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars ami
Five Stars

Re: Error while generating job

Dear Sabrina,

Before that can i follow the stpes which you mentioned?
Five Stars ami
Five Stars

Re: Error while generating job

case as opened : 
00062276

But stillw aiting for a webex session please help
One Star

Re: Error while generating job

Hello Amit,
Did u solve your issue? if Yes, can you give us a feeback please?
I encountered the same issue when connected in TAC with a user that has not the rights to deploy jobs (as admin role for example).
Regards
 
Five Stars ami
Five Stars

Re: Error while generating job

try deleting the command workspace folder and restarting the cmd line service

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog