• Index
  •  » Talend Open Studio for Data Integration » Usage, Operation
  •  » Job runs fine by itself, bombs out when ran as sub-job.

#1 2011-09-28 21:58:54

JDBurnZ
Member
Registered: 2011-08-03
Posts: 12

Job runs fine by itself, bombs out when ran as sub-job.

Tags: [bug, mssql]

Heya,

I've seen several other posts on this issue but thought I'd add my own posts, as the information present in other discussions have not been a help to me.

I have a Talend job which runs perfectly fine when ran by itself. However if I create another job and add the job as a sub-job and run it, it takes about the same amount of time to run as before, then errors out with the following message:

Exception in component tRunJob_1
java.lang.RuntimeException: Child job return 1. It doesn't terminate normally.
Exception in component tMSSqlOutput_1
java.lang.NullPointerException
    at mps.tr_import_0_1.TR_Import.tPostgresqlInput_1Process(TR_Import.java:6087)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_8Process(TR_Import.java:5643)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_7Process(TR_Import.java:5539)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_6Process(TR_Import.java:5435)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_5Process(TR_Import.java:5331)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_13Process(TR_Import.java:5227)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_4Process(TR_Import.java:5122)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_3Process(TR_Import.java:5018)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_2Process(TR_Import.java:4914)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_1Process(TR_Import.java:4810)
    at mps.tr_import_0_1.TR_Import.tPostgresqlRow_10Process(TR_Import.java:4706)
    at mps.tr_import_0_1.TR_Import.tFileInputPositional_2Process(TR_Import.java:4601)
    at mps.tr_import_0_1.TR_Import.tFileInputPositional_1Process(TR_Import.java:3192)
    at mps.tr_import_0_1.TR_Import.tPostgresqlConnection_1Process(TR_Import.java:6526)
    at mps.tr_import_0_1.TR_Import.runJobInTOS(TR_Import.java:6918)
    at mps.tr_import_0_1.TR_Import.main(TR_Import.java:6786)

    at mps.tr_start_0_1.TR_START.tRunJob_1Process(TR_START.java:439)
    at mps.tr_start_0_1.TR_START.runJobInTOS(TR_START.java:934)
    at mps.tr_start_0_1.TR_START.main(TR_START.java:802)

Most other posts I've seen also are working with MSSql related tasks, so I'm wondering if there may be a bit of a bug somewhere within the MSSql plugin.

To furthermore prove my theory, I've ran a similar sub-job utilizing only PostgreSQL, and the job runs fine.

Currently running Talend Open studio 4.2.3.r67267

Where might I report this bug?

Offline

#2 2011-09-29 07:18:13

shong
Talend team
Registered: 2007-08-29
Posts: 10310
Website

Re: Job runs fine by itself, bombs out when ran as sub-job.

Dear user

Can you please export the job item and send it to me for reproducing the problem?

Best regards
Shong


Email:shong@talend.com
Choose Talend, Enjoy Talend!
New & Event: Talend Help Center
Talend-->the leader of open source data management and application integration solutions!

Offline

#3 2011-10-05 17:54:53

JDBurnZ
Member
Registered: 2011-08-03
Posts: 12

Re: Job runs fine by itself, bombs out when ran as sub-job.

E-mail sent, haven't heard anything back regarding it.

Offline

  • Index
  •  » Talend Open Studio for Data Integration » Usage, Operation
  •  » Job runs fine by itself, bombs out when ran as sub-job.

Board footer

Powered by FluxBB