Summary: java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
Key: JENKINS-12446
URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: Linux
Reporter: aaronlab
Priority: Blocker
This issue started happening since 1.446+ (meaning, 446, 447, 448). Apparently either jenkins core or some plugin is using slf4j, but neither Jenkins, nor the plugin ships with any slf4 implementations, resulting the in following stack trace on startup...
Failed to instantiate SLF4J LoggerFactory
Reported exception:
java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.javCaused by: java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
at java.lang.ClassNotFoundException.<init>(ClassNotFoundException.java:77)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1524)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
... 22 more
I was able to get Jenkins to start fine by manually downloading the slf4j-simple directly from maven and putting it into WEB-INF/lib... but, without that file, Jenkins is 100% unusable.
http://repo2.maven.org/maven2/org/slf4j/slf4j-simple/1.6.1/slf4j-simple-1.6.1.jar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Brant Bobby commented on JENKINS-12446:
---------------------------------------
I'm experiencing the same issue. I've added an attachment with the winstone log output. I launched Jenkins using:
bq. java jenkins.war --httpPort=9000 --ajp13Port=-1
Based on the log I suspect it's the new SSHD module (introduced in 1.446) causing the problem.
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Priority: Blocker
> Attachments: winstone.log
Brant Bobby edited comment on JENKINS-12446 at 2/1/12 5:10 PM:
---------------------------------------------------------------
I'm experiencing the same issue on 1.450. I've added an attachment with the winstone log output. I launched Jenkins using:
bq. java -jar jenkins.war --httpPort=9000 --ajp13Port=-1
Based on the log I suspect it's the new SSHD module (introduced in 1.446) causing the problem.
was (Author: brant):
I'm experiencing the same issue on 1.450. I've added an attachment with the winstone log output. I launched Jenkins using:
bq. java jenkins.war --httpPort=9000 --ajp13Port=-1
Based on the log I suspect it's the new SSHD module (introduced in 1.446) causing the problem.
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Priority: Blocker
> Attachments: winstone.log
Brant Bobby edited comment on JENKINS-12446 at 2/1/12 5:10 PM:
---------------------------------------------------------------
I'm experiencing the same issue on 1.450. I've added an attachment with the winstone log output. I launched Jenkins using:
bq. java jenkins.war --httpPort=9000 --ajp13Port=-1
Based on the log I suspect it's the new SSHD module (introduced in 1.446) causing the problem.
was (Author: brant):
I'm experiencing the same issue. I've added an attachment with the winstone log output. I launched Jenkins using:
bq. java jenkins.war --httpPort=9000 --ajp13Port=-1
Based on the log I suspect it's the new SSHD module (introduced in 1.446) causing the problem.
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Priority: Blocker
> Attachments: winstone.log
Brant Bobby updated JENKINS-12446:
----------------------------------
Attachment: winstone.log
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Priority: Blocker
> Attachments: winstone.log
Kohsuke Kawaguchi commented on JENKINS-12446:
---------------------------------------------
I tried this on Tomcat 6 and 7 but couldn't reproduce this. And ditto for "java -jar jenkins.war" --- it works for me.
Those who are seeing this problem, please report your environment and versions of the relevant software so that we can diagnose this problem further.
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Priority: Blocker
> Attachments: winstone.log
Kohsuke Kawaguchi commented on JENKINS-12446:
---------------------------------------------
I wonder if you are getting the older version of slf4j-api from somewhere (such as container shared library, etc.) As discussed in http://www.slf4j.org/codes.html, missing StaticLoggerBinder is no longer an error in the version we ship in Jenkins (1.6.1).
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Priority: Blocker
> Attachments: winstone.log
SCM/JIRA link daemon commented on JENKINS-12446:
------------------------------------------------
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
maven-plugin/pom.xml
pom.xml
war/pom.xml
http://jenkins-ci.org/commit/jenkins/ef1ad6ca29c313fa0b4bc6f5dcd8344046221049
Log:
[FIXED JENKINS-12334 JENKINS-12446 JENKINS-12650]
Bundle slf4j binding to the war.
See the comment in war/pom.xml for detailed discussion.
This is fundamentally a "damned if I do, damned if I don't" situation,
but given that JENKINS-12334 is a fatal error, and the downside of
bundling the binding jar is "multiple binding" warning, it seems like
the lesser evil is to bundle it and risk some warnings.
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Priority: Blocker
> Attachments: winstone.log
Kohsuke Kawaguchi resolved JENKINS-12446.
-----------------------------------------
Assignee: Kohsuke Kawaguchi
Resolution: Fixed
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Assignee: Kohsuke Kawaguchi
> Priority: Blocker
> Attachments: winstone.log
SCM/JIRA link daemon commented on JENKINS-12446:
------------------------------------------------
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
maven-plugin/pom.xml
pom.xml
war/pom.xml
http://jenkins-ci.org/commit/jenkins/7cc71cd78ea5839bec9a4c881c00751dde9b5b5a
Log:
[FIXED JENKINS-12334 JENKINS-12446 JENKINS-12650]
Bundle slf4j binding to the war.
See the comment in war/pom.xml for detailed discussion.
This is fundamentally a "damned if I do, damned if I don't" situation,
but given that JENKINS-12334 is a fatal error, and the downside of
bundling the binding jar is "multiple binding" warning, it seems like
the lesser evil is to bundle it and risk some warnings.
Cherry-picked-from: ef1ad6ca29c313fa0b4bc6f5dcd8344046221049
> java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
> -----------------------------------------------------------------
>
> Key: JENKINS-12446
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12446
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux
> Reporter: aaronlab
> Assignee: Kohsuke Kawaguchi
> Priority: Blocker
> Attachments: winstone.log
>
>