Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Duplicate
    • 4.4.6
    • None
    • karaf
    • None

    Description

      I have encountered several SLF4J warnings when connecting using the ./bin/client command in Apache Karaf version 4.4.6. The following warnings are displayed at the beginning of the connection:

      SLF4J(W): No SLF4J providers were found.
      SLF4J(W): Defaulting to no-operation (NOP) logger implementation
      SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
      SLF4J(W): Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
      SLF4J(W): Ignoring binding found at [jar:file:/Users/niklas/Downloads/apache-karaf-4.4.6/system/org/apache/karaf/org.apache.karaf.client/4.4.6/org.apache.karaf.client-4.4.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
      SLF4J(W): See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.

      Steps to Reproduce:

      1. Download and extract Apache Karaf version 4.4.6.
      2. Navigate to the extracted directory.
      3. Start Karaf using the command ./bin/start.
      4. Use the command ./bin/client to connect.

       

      Expected Behavior:
      No SLF4J warnings should be displayed during the connection process.

       

      Actual Behavior:
      Multiple SLF4J warnings are displayed, indicating issues with SLF4J provider bindings and defaulting to a no-operation logger implementation.

       

      Environment:

      • Apache Karaf version: 4.4.6
      • Java version: OpenJDK 11.0.22

      Please investigate this issue and provide guidance on how to resolve the SLF4J warnings.

      Thank you.

      Attachments

        Issue Links

        Activity

          I confirm the issue. Thanks for the report.

           

          I'm fixing that.

          jbonofre Jean-Baptiste OnofrĂ© added a comment - I confirm the issue. Thanks for the report.   I'm fixing that.
          githubbot ASF GitHub Bot added a comment -

          PeterSuna closed pull request #1851: KARAF-7829 Override org.slf4j to 2.0.12
          URL: https://github.com/apache/karaf/pull/1851

          githubbot ASF GitHub Bot added a comment - PeterSuna closed pull request #1851: KARAF-7829 Override org.slf4j to 2.0.12 URL: https://github.com/apache/karaf/pull/1851
          githubbot ASF GitHub Bot added a comment -

          PeterSuna opened a new pull request, #1851:
          URL: https://github.com/apache/karaf/pull/1851

          Override transitive dependency version for `org.slf4j` from *1.7.32* and *1.7.35* to *2.0.12* as defined in Karaf BOM project.

          This issue arose after bumping slf4j to 2.0.12 in this commit:
          https://github.com/apache/karaf/pull/1831/commits/03354d2635441d19ff762e217348f798a19cc983#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R324

          However, some transitive dependencies still remain at version 1.7.32 and 1.7.35. See the `mvn dependency:tree` output:

          [INFO] -

          githubbot ASF GitHub Bot added a comment - PeterSuna opened a new pull request, #1851: URL: https://github.com/apache/karaf/pull/1851 Override transitive dependency version for `org.slf4j` from * 1.7.32 * and * 1.7.35 * to * 2.0.12 * as defined in Karaf BOM project. This issue arose after bumping slf4j to 2.0.12 in this commit: https://github.com/apache/karaf/pull/1831/commits/03354d2635441d19ff762e217348f798a19cc983#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R324 However, some transitive dependencies still remain at version 1.7.32 and 1.7.35. See the `mvn dependency:tree` output: [INFO] -
          githubbot ASF GitHub Bot added a comment -

          jbonofre commented on PR #1851:
          URL: https://github.com/apache/karaf/pull/1851#issuecomment-2210571169

          Just a note: this PR doesn't actually fix the problem described in KARAF-7829.
          For Karaf client slf4j issue, it's coming of the client packaging slf4j logger/binder from slf4j 1.x. I will create another PR to upgrade the client to slf4j 2.x (using `Provider` instead of `Binder`).

          githubbot ASF GitHub Bot added a comment - jbonofre commented on PR #1851: URL: https://github.com/apache/karaf/pull/1851#issuecomment-2210571169 Just a note: this PR doesn't actually fix the problem described in KARAF-7829 . For Karaf client slf4j issue, it's coming of the client packaging slf4j logger/binder from slf4j 1.x. I will create another PR to upgrade the client to slf4j 2.x (using `Provider` instead of `Binder`).

          People

            jbonofre Jean-Baptiste Onofré
            creak Niklas Neesen
            Votes:
            0 Vote for this issue
            Watchers:
            Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack