Solving slf4j: Failed to load class “org.slf4j.impl.StaticLoggerBinder”

Mayank GuptaMay 4th, 2017Last Updated: July 6th, 2022

9 17,572 3 minutes read

In this post, we feature a comprehensive article about how to solve the error slf4j: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.

You can also check this tutorial in the following video:

Solving slf4j: Failed to load class “org.slf4j.impl.StaticLoggerBinder” – Video

1. Introduction

The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, log4j). This allows the end-user to plug in the desired logging framework at deployment time.

SLF4J facilitates your code to make logging calls without binding to a specific logging implementation. This comes real handy for libraries where it is not desired to hard bind the API to a particular logging framework; the program might be using another logging implementation.

2. The slf4j: Failed to load class “org.slf4j.impl.StaticLoggerBinder” Error

While working with SLF4J, you need to provide the following three components (read jars):

SLF4J API (slf4j-api.jar) – This lets you make logging calls to SLF4J’s org.slf4j.Logger in your code (and not a specific logging implementation thus introducing logging abstraction in your code).
SLF4J Binding – This is either slf4j-log4j12.jar (for log4j logging), slf4j-jdk14.jar (for Java logging), slf4j-jcl.jar (if you’re using Commons logging) or logback-classic.jar (for logback logging). With the correct binding jar, SLF4J is able to interface between slf4j-api and underlying logging implementation.
Underlying Logging Implementation – Here you provide the underlying logging library which will actually do the logging for your program. SLF4J will delegate logging calls to this library.

Among all these components, if you miss the 2nd one, then you will run into the Failed to load class “org.slf4j.impl.StaticLoggerBinder” message and the org.slf4j.impl.StaticLoggerBinder is found in any of the SLF4J’s binding jar.

Let’s try some code and see how we can fix this.

3. Example of the error Failed to load class “org.slf4j.impl.StaticLoggerBinder” in slf4j

3.1 Create a Maven Project

We will create a bare minimum Maven project. Once you have the Maven installed and running on your machine, issue the following command from the command line.

mvn archetype:generate -DgroupId=com.javacodegeeks -DartifactId=slf4-spring-boot -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false

In this example, Maven will manage dependencies for us and we don’t need to download any jars explicitly.

3.2 Add Maven Dependencies

Add dependency just for slf4j-api.

pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
 
  <groupId>com.javacodegeeks</groupId>
  <artifactId>slf4jconfig-javalogging</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <packaging>jar</packaging>
 
  <name>slf4jconfig-javalogging</name>
  <url>http://maven.apache.org</url>
 
  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>
 
  <dependencies>
    <dependency>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-api</artifactId>
        <version>1.7.25</version>
    </dependency>
  </dependencies>
</project>

3.3 Test Class

HelloJavaLogging.java

package com.javacodegeeks.slf4jconfig_javalogging;
 
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
 
/**
 * HelloJavaLogging!
 *
 */
public class HelloJavaLogging 
{
    public static void main( String[] args )
    {
        Logger logger = LoggerFactory.getLogger(HelloJavaLogging.class);
        logger.info("This is how you configure Java Logging with SLF4J");
    }
}

Run the code.

Output

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.

It seems like we missed the binding jar for SLF4J and Java Logging. Let’s add slf4j-jdk14 jar file and see if it solves the problem.

Add the following lines in your pom.xml:

<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-jdk14</artifactId>
    <version>1.7.25</version>
</dependency>

Note: We don’t need to provide the underlying logging framework’s jar in this case as we are using Java Logging. The implementation is provided in JDK.

Let’s re-run the code.

Output

May 03, 2017 8:10:40 PM com.javacodegeeks.slf4jconfig_javalogging.HelloJavaLogging main
INFO: This is how you configure Java Logging with SLF4J

Finally, we got the output we desired.

4. slf4j: Failed to load class “org.slf4j.impl.StaticLoggerBinder” – Summary

Remember, the absence of SLF4J Binding runs into Failed to load class “org.slf4j.impl.StaticLoggerBinder” Error.

Notes:

As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation.
As of SLF4J version 1.8.0, the static binder mechanism will be deprecated. StaticLoggerBinder is likely to be removed in future releases of SLF4J.