You are not logged in.
Announcement
Unanswered posts
|
- Index
- » Usage, Operation
- » Exporting a job that contains subjobs doesn't work
Post a reply
Topic review (newest first)
- bazinou
- 2010-05-27 10:32:31
A little background, we just recently migrated from TOS 3.2.1 to TIS 4.0.1 (export jobs from TOS and import into TIS). On my client machine (windows 32, java 1.6), I have both TOS and TIS installed.
Also when I open some of the jobs after import, it prompts for context updates - for whatever reasons. I saved the job and export and still have this issue....
I have the same problem, and more (.jar bigger than the same exported with TOS 3.2) ....
http://www.talendforge.org/forum/viewtopic.php?id=10875
I've created a project test case that produce the problem an send it to the Talend team, but no response at this time.
- saladspoon
- 2010-05-27 00:24:28
Talend, any update on this? I have the same problem on TIS 4.0.1. Exporting war with subjobs - sometimes, the subjob only has the manifest folder, not the folder contain the classes. Other times, it contains classes of other subjobs -- causing massive bloating of the war file. Also, there are cases where the subjob classes are referencing different job classes altogether!
A little background, we just recently migrated from TOS 3.2.1 to TIS 4.0.1 (export jobs from TOS and import into TIS). On my client machine (windows 32, java 1.6), I have both TOS and TIS installed.
Also when I open some of the jobs after import, it prompts for context updates - for whatever reasons. I saved the job and export and still have this issue....
Please help, very stuck.
- Lee Eason
- 2009-10-07 22:29:06
I ran into this exact issue today and after quite a bit of searching and troubleshooting I found that I have reproduced this bug in version 3.2.0 RC1 r29643-20090911-0631. I am running Windows XP (32bit) and Java 1.6.0_15. What I am seeing is that any job that is a subjob of another job will not be exported properly as an autonomous job. The .jar files it spits out are 1KB. If you take those same jobs out of the subjob or export them independently then the export works fine and you can copy those JARs back into the main job to fix the problem.
- shong
- 2009-06-09 03:48:57
Hello EOSS
Please check if there are some blank space in your export path.
Best regards
shong
- EOSS
- 2009-06-08 17:41:50
FYI, I am using TOS 3.1.0 ans still encountering the problem. JAR files of sub-jobs are empty.
O.S. Windows VISTA
- pravu
- 2009-05-15 09:32:10
Hi,
I am still using 2.4.3 because I got some other defects in 3.0.
Is it all right to use version 3.1.0
Thanks and Regards,
Pravu Mishra.
- nSmolyniec
- 2009-05-14 18:00:05
Hi everybody!
Well, for the moment, I do not encounter this bug anymore with TOS 3.1.0 (whereas it still occurs in 3.0.4).
Some stuff may have been improved and it's nice to see the "progress information".
Strange for you kolojay.
Best regards,
Nicolas
- kolojay
- 2009-05-05 13:33:21
And also still the same bug with the new version TOS 3.1, that has been released today. I think it must be caused by varios factors on some systems, maybe it's a Java problem?!
Best regards
Christian
- nSmolyniec
- 2009-04-22 18:59:37
Hi again,
Still the same bug, whatever the options picked.
No log entry for it into the Talend logs.
Best regards,
Nicolas
- nSmolyniec
- 2009-04-21 13:59:57
Hello,
I've got the same in 32bit (on Win XP & TOS 3.0.4).
I'll look at the logs later.
Bye,
Nicolas
- kolojay
- 2009-04-21 12:44:34
Okay, obviously I'm not the only user with this Bug. Currently my version number is 3.0.4.r22547 and I'm using Windows XP on a 64 bit machine. May the 64 bit be the problem? Because the problem is there there...
Maybe on 27th April it will be better with Open Studio 3.1?
Best regards,
Christian
- youssef
- 2009-04-17 16:47:57
Hi all,
I'm using Talend 3.0.4 on windows xp and everything is ok. I can export jobs including subjobs with no problems. I can't reproduce your "bug".
Regards,
Youssef
- nSmolyniec
- 2009-04-17 16:31:14
Hello,
I confirm there is a bug.
When you export to an autonomous job, the jar file of the main job is ok, but not those of the child jobs.
For the moment, I've found one solution : as the export to a webservice seems to be ok, I get the jar files of the subjobs from this one!
Hope all will be ok soon.
Regards,
Nicolas
P.S. : I'm on Talend 3.0.4
- Volker Brehm
- 2009-03-26 16:06:53
Yes,
I've the same effect, jars are empty and no log entry.
TOS 3.0.3 / SUN VM 1.6 / Windows
@Talend: Is there any additional debug capability we could activate?
Bye
Volker
- kzone
- 2009-03-26 16:02:30
hi,
too much work this morning to look at .log , sorry !
so clean my log file and launch Talend ...no special infos i think
!SESSION 2009-03-26 15:52:19.195 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=fr
Command-line arguments: -os linux -ws gtk -arch x86
!ENTRY org.talend.libraries 1 0 2009-03-26 15:52:24.925
!MESSAGE 2009-03-26 15:52:24,923 INFO org.talend.repository.model.ProxyRepositoryFactory - raulier@landes-mutualite.fr logged on RDO-test-context
.... export job script ( no more logs written) !
Still have subjob jar empty except manifest !
....