SLF4J: Faild to load class in TOS 6.x about talendcomp_tjobinstance HOT 8 CLOSED

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

from talendcomp_tjobinstance.

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_load__pg job_instance_id: 132
2021-10-12 15:45:14|EGEAUc|EGEAUc|EGEAUc|25016|ETLFRAMEWORK|template_demo_no_context_load__pg|_AEkDECtsEeyJ0sp_R7CZAQ|1.0|dev1||begin||`

from talendcomp_tjobinstance.

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.

from talendcomp_tjobinstance.

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 ;-)

from talendcomp_tjobinstance.

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

from talendcomp_tjobinstance.

It ok to close

from talendcomp_tjobinstance.

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

from talendcomp_tjobinstance.

I will close this ticket after updating the component.

from talendcomp_tjobinstance.