
Contributor
2015-07-10
12:00 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
154 Views
2 Replies

Anonymous
Not applicable
2015-07-13
04:15 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
154 Views

Anonymous
Not applicable
2015-07-13
10:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This can be achieved in 5.4.1 version, check this:
Dynamic log4j file per job
Dynamic log4j file per job
154 Views
