-
Bug
-
Resolution: Fixed
-
Critical
-
core 1.606
support bundle 2.20
With support bundle plugin installed, when I create a new logger and let the logger classname field empty, Jenkins crashes when I click Save button.
On save, Jenkins starts to write tons of exception logs and is not responsible anymore. Killing the JVM is the only way to stop it doing this.
Logged exception looks like this one:
Exception in thread "RequestHandlerThread[#10]" java.lang.ClassCircularityError: hudson/logging/LogRecorder at com.cloudbees.jenkins.support.impl.JenkinsLogs$CustomHandler.publish(JenkinsLogs.java:507) at java.util.logging.Logger.log(Logger.java:616) at java.util.logging.Logger.doLog(Logger.java:641) at java.util.logging.Logger.log(Logger.java:730) at org.eclipse.jetty.util.log.JavaUtilLog.warn(JavaUtilLog.java:70) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:698) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)
On 1.580, faulty configuration is saved on disk. To restart the instance, faulty configuration file $JENKINS_HOME/log/<faulty>.xml must be removed.
On 1.606, configuration is not saved, so restarting the instance works.
- is related to
-
JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed
- Resolved
- relates to
-
JENKINS-55014 Deadlocking around support-core-plugin log publishing
- Closed
-
JENKINS-62472 Require confirmation before configuring root logger to high log level
- Open
- links to