[JIRA] (JENKINS-38534) ProcessKillingVeto.all() forces Jenkins class to be instantiated on remote agents

[stephenconno...@java.net (JIRA)]

Title: Message Title

stephenconnolly created an issue   Jenkins / JENKINS-38534 ProcessKillingVeto.all() forces Jenkins class to be instantiated on remote agents Issue Type: Improvement Assignee: stephenconnolly Components: core Created: 2016/Sep/27 11:48 AM Priority: Minor Reporter: stephenconnolly We have a plugin that is instantiating LocalProc from the agent JVM and is hitting a Caused by: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins at hudson.util.ProcessKillingVeto.all(ProcessKillingVeto.java:77) at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:237) at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:566) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:592) at hudson.util.ProcessTree.killAll(ProcessTree.java:141) at hudson.Proc$LocalProc.destroy(Proc.java:379) at hudson.Proc$LocalProc.kill(Proc.java:371) ... error. The root cause of this issue is that the ProcessKillingVeto.all method forces the Jenkins class to be loaded... this is a bad thing as agents are not supposed to try and instantiate the Jenkins class (that some plugins can sometimes managed to succeed in instantiating the Jenkins class on a remote agent is neither here nor there... we should not be trying to instantiate it at all) Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.