Problem with log4j in subjob

One Star

Problem with log4j in subjob

Hello,

I run serveral jobs using tRunJob. In the Main Job I use tInitLog4j for use of log4j. In the main job, that works fine.

Now my goal is to have a seperat logging file for each subjob. The initialization of tInitLog4j doesn't work, even with the checkbox "Lock Log4j configuration" disabled.
Also without own initialization in the subjob, tLog4j doesn't log into the file of the main job.

Has anyone ever worked with different logfiles for subjobs?

Any help would be apreceated.

Thanks in advance

Henning

Moderator

Re: Problem with log4j in subjob

Hi,
Have you tried to use tStatCatcher, tLogCatcher and tFlowmeterCatcher which all have predefined schemas. In your job settings, you can choose to write these logs to console, file or database - or all 3 at the same time. The stats they gather are great because they give you an end-to-end view of your job run. In there, you'll see when each child job started and ended.


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.
Six Stars

Re: Problem with log4j in subjob

This can be achieved in 5.4.1 version, check this:
Dynamic log4j file per job

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