Hi Arbi, On 29.04.2025 17:55, Arbi Sookazian wrote:
In dev envmt, I am using slf4j-api-2.0.6.jar, in QA we are using slf4j-api-1.7.25.jar. SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details. SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier. SLF4J: Ignoring binding found at [jar:file:/C:/sw/apache-tomcat-7.0.84/shared/log4j-slf4j-impl-2.9.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
SLF4J 2 was released in 2022 and introduced breaking changes for SLF4J implementation providers. You need to use `log4j-slf4j2-impl` (<https://logging.apache.org/log4j/2.x/components.html#log4j-slf4j2-impl>) instead of `log4j-slf4j-impl` (<https://logging.apache.org/log4j/2.x/components.html#log4j-slf4j-impl>).
log4j-core-2.9.1.jar
Can you upgrade to Log4j Core 2.24.3? If the you use JRE 7 on your QA server, at least upgrade to Log4j Core 2.12.4. Debugging problems on a version published in 2018 is not very useful, they might have been solved by now.
Piotr --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
