Nov 16, 2015 6:54:59 AM net.bull.javamelody.JavaLogger warn
WARNING: exception while collecting data
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N
at hudson.remoting.Channel$2.adapt(Channel.java:810)
at hudson.remoting.Channel$2.adapt(Channel.java:805)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
at net.bull.javamelody.RemoteCallHelper.collectDataByNodeName(RemoteCallHelper.java:169)
at net.bull.javamelody.RemoteCallHelper.collectJavaInformationsListByName(RemoteCallHelper.java:179)
at net.bull.javamelody.NodesCollector.collectWithoutErrorsNow(NodesCollector.java:154)
at net.bull.javamelody.NodesCollector.collectWithoutErrors(NodesCollector.java:143)
at net.bull.javamelody.NodesCollector$1.run(NodesCollector.java:87)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N
at net.bull.javamelody.RemoteCallHelper$DelegatingTask.call(RemoteCallHelper.java:130)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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)
at ......remote call to master_git(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel$2.adapt(Channel.java:808)
... 9 more
seems to have started happening after an upgrade from an old version of both jenkins and the plugin
The issue persisted across reboots and plugin reinstalls. However during the reinstall I noticed it seems to be related to JENKINS_HOME/cache/jars. I have a non-default JENKINS_HOME and $HOME/.jenkins exists with 000 permissions. The install process tried to write jars to $HOME/.jenkins/cache/jars for some reason. After I allowed it, it created a bunch of jar files there and the missing class errors disappeared from the logs.
I was unable to reproduce the issue on my test instance that runs a newer version (1.631)
I'm able to reproduce the issue in Jenkins 1.632. We have installed Jenkins in a custom location and use JENKINS_HOME. However, I couldn't find any directory called $JENKINS_HOME/.jenkins or $HOME/.jenkins (for the user running Jenkins instance). The error happens at runtime and we see it almost every hour in the Jenkins log files.
Aditya Joshi: Can you try creating empty writable directories so that $HOME/.jenkins/cache/jars exists during plugin installation? If that helps, I believe this bug shoud be reopened and renamed to "installing the monitoring plugin does not respect custom JENKINS_HOME when it comes to jar cache".
Thanks Tomasz, I don't see the above mentioned error anymore after creating the empty writable directory $HOME/.jenkins/cache/jars and reinstalling the monitoring plugin. I do get the error mentioned in https://issues.jenkins-ci.org/browse/JENKINS-29257 but that seems to be a separate issue.
Thanks Tomasz, I don't see the above mentioned error anymore after creating the empty writable directory $HOME/.jenkins/cache/jars and reinstalling the monitoring plugin. I do get the error mentioned in https://issues.jenkins-ci.org/browse/JENKINS-29257 but that seems to be a separate issue.