search

jlolling / talendcomp_tJobInstance

Talend User Components to work with the cimt framework for batch jobs. These components are developed as cooperation between cimt AG and Jan Lolling
Apache License 2.0
14 stars 7 forks source link

SLF4J: Faild to load class in TOS 6.x #27

Closed mattywausb closed 12 months ago

mattywausb commented 2 years ago

Release 8.2: When tJobinstanceStart is used in TOS 6.3 or 6.5 I get a warning on stderr (or at least in red) at start:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Further processing is normal.

mattywausb commented 2 years ago

Complete Console output at start: `Starte Job template_demo_no_context_load__pg am 17:45 12/10/2021.

[statistics] connecting to socket on port 3492 [statistics] connected SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Job Instance Start of: template_demo_no_context_loadpg job_instance_id: 132 2021-10-12 15:45:14|EGEAUc|EGEAUc|EGEAUc|25016|ETLFRAMEWORK|template_demo_no_context_loadpg|_AEkDECtsEeyJ0sp_R7CZAQ|1.0|dev1||begin||`

jlolling commented 2 years ago

This error message can be ignored. It means the used logging framework in the component is not ready to run. I have recently decided to replace the SL4J framework with Log4J v2 which is used as default in Talend jobs.

jlolling commented 2 years ago

One problem is, TOS 6 use Log4J v1 and TOS 7.x use Log4J v2. I cannot support both at the same time. So I have decided to use Log4J v2 and ship the library with the component to enable logging also in Talend 6. But I have not tested it yet for Talend 6 because I do not have installed Talend 6. Most customer I know have already switched to Talend 7 (including my former employer ;-)

jlolling commented 2 years ago

So, it is actually not a bug, it is an incomplete configuration. The component works well also without a working internal logging.

mattywausb commented 2 years ago

Ok. its just, "Red letters" in the console are alway getting attention

mattywausb commented 2 years ago

It ok to close

jlolling commented 2 years ago

I know, the next release of this component will using Log4J v2 and will not show these red output anymore.

jlolling commented 2 years ago

I will close this ticket after updating the component.