Gatling 3.10.3 -> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"

After switching to Gatling 3.10.3 I was starting getting next messages in console:

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

Debug log file was created but missing all logs (locally in VS Code).
Based on ChatGPT suggestions: i`ve added a new dependency in my pom.xml and it solved the issue.

    <!-- <dependency>
    </dependency> -->

Qustion: Is it expected in a new Gatling version or it can by my project set-up issue (when using open saml libs)?

Have you taken some time to check the upgrade notes? Gatling - Upgrading from 3.9 to 3.10

If you’re bringing your own libraries into Gatling’s classpath, it’s your responsibility to deal with dependency versions clashes.

Here, it seems opensaml still depends on slf4j 1. Basically, the Java ecosystem is currently split 50/50 between slf4j 1 and 2.

Somehow, your build tool (maven?) is picking opensaml’s slf4j 1 over our slf4j 2. You must then make sure to have the proper logback version, see Logback Dependencies

Note: I’ve updated the upgrade guide. Hopefully things are clearer now.

Thanks for clarification!
Now it is clear :call_me_hand:.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.