Post a reply

Write your message and submit

Options

Click in the dark area of the image to send your post.

Go back

Topic review (newest first)

beproulx
2012-02-13 17:30:17

I double checked what I was doing and am still not successful in exporting a job from a branch that refers to a joblet in a reference project that also resides on a branch.  I will enter an issue in BugTracker.

beproulx
2012-02-08 01:06:44

I'm not sure you are missing a step but thank you for trying to reproduce the problem.  Before I enter a case I want to double check to make sure I am not trying to use bad joblets from the reference project's branch.  I just have not had a chance to do that yet.
FYI - It's a Linux server where TAC, SVN, and commandline reside.

pedro
2012-02-07 07:10:09

Hi

I try to reproduce this issue both in Windows and Linux environments by creating joblets in reference project and exporting job in commandline, but failed.
Do I miss some detail?

If not, please create issue at BugTracker.

Regards,
Pedro

beproulx
2012-02-03 18:04:35

We have a a job residing in a project branch that refers to joblets in a referenced project (which also is a branch).

We are able to export that job using the Studio but when using the following commands with CommandLine the error below occurs.


initRemote http://myserver.com:8080/org.talend.administrator
logonProject -pn MYPROJ -ul who@company.com -up XXX -br RC2
exportJob "JB_SEC_USER_SYNCHRONIZE_RC2" -jv "0.1" -af "JB_SEC_USER_SYNCHRONIZE_RC2-0.1" -dd "/talend/poc/wfancore.06.03.qa.int.appdev/stage"


FAILURE:

talend> getCommandStatus 2
FAILED at Wed Feb 01 16:37:49 EST 2012
                                      exception : org.talend.commandline.client.command.CommandStatusWrapException: org.
talend.commons.exception.PersistenceException: Process cannot be opened because some used components <JBL_LOGGING_ETL_LO
G,JBL_LOGGING_ETL_LOG_ERR> are not loaded
                                                at org.talend.designer.core.ui.editor.process.Process.checkLoadNodes(Unk
nown Source)
                at org.talend.commandline.util.JobHandler.loadProcess(Unknown Source)
                                                                                        at org.talend.commandline.util.J
obHandler.generateCode(Unknown Source)
                                        at org.talend.commandline.util.JobHandler.init(Unknown Source)
                                                                                                        at org.talend.co
mmandline.command.CommandProcessor.doExportJob(Unknown Source)
                                                                at org.talend.commandline.command.CommandProcessor.expor
tJob(Unknown Source)
                        at org.talend.commandline.command.CommandProcessorSwitch.caseExportJobCommand(Unknown Source)

at org.talend.commandline.client.util.CommandAbstractSwitch.doSwitch(Unknown Source)
                                                                                        at org.talend.commandline.comman
d.CommandConsumer.executeCommand(Unknown Source)
                                                        at org.talend.commandline.command.CommandConsumer.execute(Unknow
n Source)
                at org.talend.commandline.mode.ServerCommandLine$CommmandConsumerRunnable.run(Unknown Source)
                                                                                                                at java.
lang.Thread.run(Thread.java:619)


The JBL_LOGGING_ETL_LOG and JBL_LOGGING_ETL_LOG_ERR mentioned in the error are joblets in the reference project.

Has anyone experienced a similar problem?

Board footer

Powered by FluxBB