[resolved] tLogCatcher does not catch Java Exception

[Anonymous]

Hi,
I have a job which does some work, and calls some subjobs. This main work is connected by a flow and has one start point (highlighted as green).
I want every Java exception been kept by tLogCatcher.
I created a tLogCather job as standalone job (not within the main flow). One sub job follows the tLogCatcher. The sub job shall make some entries in my databases log-table. The tLogCatcher is also highlighted as green and "catch Java Exceptions" is checked, tDie and tWarn isnt checked.
I found this Thread which unfortunately stays unsolved. There one told about a checkbox for multithreading. I do not have such an option for tLogCatcher.
Well when executing my job the console shows an Java exception. I do not understand why my log job isnt called.
One thought, I was not able to find an answer on is if I need to create a tlogCather on every subjob or if its enough to have one on the main job.
For further imagination here are some Screenshots about my job and the options of tLogCatcher.
Any help would be grateful. Thanks in advance.

[Anonymous]

Catching the handled erros by components I have to use run-if (which i still do for manual logging)

for XSD validation, when an error occured due to non conforme schema, you've got red information telling you about the problem.
BUT it's not an error about the component ... so onComponentError or on SubJobError cannot work !
for that reason use run-if
about logs errors you can configure which one you want to catch.
regards
laurent

[Anonymous]

test with onComponentError + twarn
test run-if + twarn 
both of them are log on console
result with onComponent error :

Starting job xsdValidation at 11:46 03/09/2014.
 connecting to socket on port 3688
 connected
There is an Error on line 35 : Contenu non autorisé dans la section de fin.
 File is Invalid
2014-09-03 11:46:38|mdrMTw|mdrMTw|mdrMTw|SANDBOX|xsdValidation|Default|4|tWarn|tWarn_2|XML Valide|42
 disconnected
Job xsdValidation ended at 11:46 03/09/2014. 

result with run-if 

Starting job xsdValidation at 11:50 03/09/2014.
 connecting to socket on port 3601
 connected
There is an Error on line 35 : Contenu non autorisé dans la section de fin.
 File is Invalid
2014-09-03 11:50:46|sxquUz|sxquUz|sxquUz|SANDBOX|xsdValidation|Default|4|tWarn|tWarn_1| File is Invalid|42
 disconnected
Job xsdValidation ended at 11:50 03/09/2014. 

if you want to catch the cause of xsd is invalid , use the global var :
 

((String)globalMap.get("tXSDValidator_1_XSD_ERROR_MESSAGE"))

the whole message in tWarn (error one) :

((String)globalMap.get("tXSDValidator_1_ERROR_MESSAGE")) + "   " +  ((String)globalMap.get("tXSDValidator_1_XSD_ERROR_MESSAGE"))

for the result :

Starting job xsdValidation at 11:53 03/09/2014.
 connecting to socket on port 3795
 connected
There is an Error on line 35 : Contenu non autorisé dans la section de fin.
 File is Invalid
2014-09-03 11:53:30|lKcovM|lKcovM|lKcovM|SANDBOX|xsdValidation|Default|4|tWarn|tWarn_1| File is Invalid   There is an Error on line 35 : Contenu non autorisé dans la section de fin.|42
 disconnected
Job xsdValidation ended at 11:53 03/09/2014. 

hope it helps
regards
laurent

[Anonymous]

hey
you wrote "about logs errors you can configure which one you want to catch." and attached a screenshot.
What does this option mean? Is it like o over-global-tLogCatcher which prints all errors/ exception into console?
Does this option exists instead of other tLogCather or exist in addition? (Means on runtime errors its printed by this option to conosle and additionally the component tLogcather is triggered because of the exception or does then no other tLogCather be called?)

[Anonymous]

Seems to be a little confused about stats&logs and different way to use them.
please, read about that : 
https://help.talend.com/pages/viewpage.action?pageId=19426390
https://help.talend.com/pages/viewpage.action?pageId=19426977#Raa97258
For a talend project, we usually have a generic strategy about stats&logs, that we define in project setting (log in file or db)
for unit test, we temporarily switch to local setting and write in console for checking some infos.
but it's different way to do the some things catch information about logs, stats & meter data.
Because component catcher have fixed schema  to be use by AMC (activity monitoring center ... a graphic interface),
We use tLogCatcher (and other catcher) only to write & aggregate more information.
hope it help
Done some webinar & training about those features , play with them to understand how they work ...
regards

[Anonymous]

Thanks much for help, marked post as resolved.

[Anonymous]

Hi,
I have created a Talend Job using toracleinput and tjasperoutput components. My job ran successfully without any errors when I ran the job in Talend tool but when I convert to jar file and run in server, I end up with the below exception, and the exact exception is not getting catched. I have used tlogcatcher to catch the java exceptions. Can anybody help me on this.

[Anonymous]

Hi 
I see this topic has been marked as resolved. I think you have resolved the issue, feel free to reopen it if you still have any troubles. 
Best regards
Shong

[Anonymous]

Hi Talend Team,
I have a job and I put tWarn and tDie in typical steps and put tLogcatecher and route its output to tFileoutputdelimited.
But after run the job outfile contains one row which "this is a warning" it doesn't capture all warning logs and die logs.
Please help me on this.