Jenkins version 2.387.1

I’m seeing this exception when i’m updating Jenkins from 2.375.4 to 2.387.1.
when I backtrack to 2.375.4. the exception is removed and I can re-start my Jenkins

2023-04-03 12:17:18.520+0000 [id=119194]        INFO    hudson.lifecycle.Lifecycle#onStatusUpdate: Restart in 5 seconds
2023-04-03 12:17:23.521+0000 [id=119194]        INFO    hudson.lifecycle.Lifecycle#onStop: Stopping Jenkins as requested by hamidxp
2023-04-03 12:17:23.525+0000 [id=119194]        INFO    hudson.lifecycle.Lifecycle#onStatusUpdate: Stopping Jenkins
2023-04-03 12:17:23.551+0000 [id=119194]        INFO    jenkins.model.Jenkins$16#onAttained: Started termination
2023-04-03 12:17:23.568+0000 [id=119194]        INFO    o.j.p.p.m.d.PipelineMavenPluginH2Dao#close: Termination of the DAO Requested
2023-04-03 12:17:23.716+0000 [id=119194]        INFO    c.zaxxer.hikari.HikariDataSource#close: HikariPool-1 - Shutdown initiated...
2023-04-03 12:17:23.720+0000 [id=119194]        INFO    c.zaxxer.hikari.HikariDataSource#close: HikariPool-1 - Shutdown completed.
2023-04-03 12:17:23.720+0000 [id=119194]        INFO    jenkins.model.Jenkins$16#onAttained: Completed termination
2023-04-03 12:17:23.720+0000 [id=119194]        INFO    jenkins.model.Jenkins#_cleanUpDisconnectComputers: Starting node disconnection
2023-04-03 12:17:23.980+0000 [id=119194]        INFO    jenkins.model.Jenkins#_cleanUpShutdownPluginManager: Stopping plugin manager
2023-04-03 12:17:24.009+0000 [id=119194]        INFO    jenkins.model.Jenkins#_cleanUpPersistQueue: Persisting build queue
2023-04-03 12:17:24.016+0000 [id=119194]        INFO    jenkins.model.Jenkins#_cleanUpAwaitDisconnects: Waiting for node disconnection completion
2023-04-03 12:17:24.020+0000 [id=119194]        SEVERE  jenkins.model.Jenkins#_cleanUpPluginServletFilters: Failed to stop filters
java.lang.ClassNotFoundException: net.bull.javamelody.MonitoringInitialContextFactory
        at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)
        at jenkins.util.URLClassLoader2.findClass(URLClassLoader2.java:35)
        at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:587)
        at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
Caused: java.lang.NoClassDefFoundError: net/bull/javamelody/MonitoringInitialContextFactory
        at net.bull.javamelody.FilterContext.destroy(FilterContext.java:472)
        at net.bull.javamelody.MonitoringFilter.destroy(MonitoringFilter.java:176)
        at net.bull.javamelody.PluginMonitoringFilter.destroy(PluginMonitoringFilter.java:74)
        at hudson.util.PluginServletFilter.cleanUp(PluginServletFilter.java:185)
        at jenkins.model.Jenkins._cleanUpPluginServletFilters(Jenkins.java:3908)
        at jenkins.model.Jenkins.cleanUp(Jenkins.java:3605)
        at hudson.lifecycle.UnixLifecycle.restart(UnixLifecycle.java:70)
        at jenkins.model.Jenkins$19.run(Jenkins.java:4533)
2023-04-03 12:17:24.020+0000 [id=119194]        INFO    hudson.lifecycle.Lifecycle#onStatusUpdate: Jenkins stopped
Running from: /data/ci/jenkins/war/jenkins.war
2023-04-03 12:17:24.858+0000 [id=1]     INFO    winstone.Logger#logInternal: Beginning extraction from war file
2023-04-03 12:17:24.947+0000 [id=1]     WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath
2023-04-03 12:17:25.021+0000 [id=1]     INFO    org.eclipse.jetty.server.Server#doStart: jetty-10.0.12; built: 2022-09-14T01:54:40.076Z; git: 408d0139887e27a57b54ed52e2d92a36731a7e88; jvm 17.0.2+8-86
2023-04-03 12:17:25.357+0000 [id=1]     INFO    o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
2023-04-03 12:17:25.435+0000 [id=1]     INFO    o.e.j.s.s.DefaultSessionIdManager#doStart: Session workerName=node0

Looking at https://github.com/search?q=org%3Ajenkinsci+net.bull.javamelody&type=code&p=1 it looks like the only one using that class is GitHub - jenkinsci/monitoring-plugin: Jenkins monitoring plugin or GitHub - jenkinsci/huaweicloud-mastermonitor-plugin: huaweicloud master monitor

looks like Monitoring has a fix for it.

So usual advice of “make sure everything is up to date before reporting issues” applies.

If it doesn’t fix it, create an issue for that plugin.

1 Like

Thanks for your help