java.io.FileNotFoundException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Building on a dumb slave fails if a enable "Deploy artifacts to Artifactory". The error I get is: {code} ... Parsing POMs [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/data/builder/node/workspace/my-job/2.0.2 -cp /data/builder/node/maven3-agent.jar:/data/builder/node/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/builder/node/tools/maven-3-latest /data/builder/node/slave.jar /data/builder/node/maven3-interceptor.jar 44156 Exception in thread "main" java.io.FileNotFoundException: /data/builder/node/workspace/my-job/2.0.2 at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.loadGlob(ConfigurationParser.java:336) at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:247) at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:135) at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:132) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:106) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:63) ERROR: Failed to launch Maven. Exit code = 1 Skipping sonar analysis due to bad build status FAILURE Finished: FAILURE {code} When I run this build on the master node, there is no problem. The corresponding (correct) log-part is: {code} ... Parsing POMs [workspace] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/opt/jenkins/plugins/artifactory/WEB-INF/lib -cp /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/opt/jenkins/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /opt/jenkins/tools/maven-3-latest /opt/jenkins/war/WEB-INF/lib/remoting-1.419.jar /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 34663 <===[JENKINS REMOTING CAPACITY]===> channel started Executing Maven: -B -f /opt/jenkins/jobs/my-job/workspace/pom.xml clean install [INFO] Scanning for projects... ... {code} Notice the different {{-Dm3plugin.lib}} setting. On the remote slave the {{/data/builder/node/workspace/my-job/2.0.2}} does not exist.
    via by Ivar Kanters,
  • Building on a dumb slave fails if a enable "Deploy artifacts to Artifactory". The error I get is: {code} ... Parsing POMs [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/data/builder/node/workspace/my-job/2.0.2 -cp /data/builder/node/maven3-agent.jar:/data/builder/node/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/builder/node/tools/maven-3-latest /data/builder/node/slave.jar /data/builder/node/maven3-interceptor.jar 44156 Exception in thread "main" java.io.FileNotFoundException: /data/builder/node/workspace/my-job/2.0.2 at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.loadGlob(ConfigurationParser.java:336) at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:247) at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:135) at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:132) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:106) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:63) ERROR: Failed to launch Maven. Exit code = 1 Skipping sonar analysis due to bad build status FAILURE Finished: FAILURE {code} When I run this build on the master node, there is no problem. The corresponding (correct) log-part is: {code} ... Parsing POMs [workspace] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/opt/jenkins/plugins/artifactory/WEB-INF/lib -cp /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/opt/jenkins/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /opt/jenkins/tools/maven-3-latest /opt/jenkins/war/WEB-INF/lib/remoting-1.419.jar /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 34663 <===[JENKINS REMOTING CAPACITY]===> channel started Executing Maven: -B -f /opt/jenkins/jobs/my-job/workspace/pom.xml clean install [INFO] Scanning for projects... ... {code} Notice the different {{-Dm3plugin.lib}} setting. On the remote slave the {{/data/builder/node/workspace/my-job/2.0.2}} does not exist.
    via by Ivar Kanters,
  • Building on a dumb slave fails if a enable "Deploy artifacts to Artifactory". The error I get is: {noformat}... [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/data/builder/node/workspace/my-job/2.0.3 -cp /var/buildnode/maven3-agent.jar:/var/buildnode/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/buildnode/tools/maven-3-latest /var/buildnode/slave.jar /var/buildnode/maven3-interceptor.jar 53699 Exception in thread "main" java.io.FileNotFoundException: /data/builder/node/workspace/my-job/2.0.3 at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.loadGlob(ConfigurationParser.java:336) at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:247) at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:135) at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:132) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:106) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:63) ERROR: Failed to launch Maven. Exit code = 1 ... {noformat} When I run this build on the master node, there is no problem. The corresponding (correct) log-part is: {noformat} ... [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/opt/jenkins/plugins/artifactory/WEB-INF/lib -cp /var/buildnode/maven3-agent.jar:/var/buildnode/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/buildnode/tools/maven-3-latest /var/buildnode/slave.jar /var/buildnode/maven3-interceptor.jar 53699 <===[JENKINS REMOTING CAPACITY]===> channel started Executing Maven: -B -f /opt/jenkins/jobs/my-job/workspace/pom.xml clean install [INFO] Scanning for projects ... {noformat} Notice the different -Dm3plugin.lib setting. On the remote slave the /data/builder/node/workspace/my-job/2.0.3 does not exist. I also created this issue on Jenkins-ci (see https://issues.jenkins-ci.org/browse/JENKINS-10259) I think this is really a plugin problem.
    via by Ivar Kanters,
  • Building on a dumb slave fails if a enable "Deploy artifacts to Artifactory". The error I get is: {noformat}... [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/data/builder/node/workspace/my-job/2.0.3 -cp /var/buildnode/maven3-agent.jar:/var/buildnode/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/buildnode/tools/maven-3-latest /var/buildnode/slave.jar /var/buildnode/maven3-interceptor.jar 53699 Exception in thread "main" java.io.FileNotFoundException: /data/builder/node/workspace/my-job/2.0.3 at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.loadGlob(ConfigurationParser.java:336) at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:247) at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:135) at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:132) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:106) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:63) ERROR: Failed to launch Maven. Exit code = 1 ... {noformat} When I run this build on the master node, there is no problem. The corresponding (correct) log-part is: {noformat} ... [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/opt/jenkins/plugins/artifactory/WEB-INF/lib -cp /var/buildnode/maven3-agent.jar:/var/buildnode/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/buildnode/tools/maven-3-latest /var/buildnode/slave.jar /var/buildnode/maven3-interceptor.jar 53699 <===[JENKINS REMOTING CAPACITY]===> channel started Executing Maven: -B -f /opt/jenkins/jobs/my-job/workspace/pom.xml clean install [INFO] Scanning for projects ... {noformat} Notice the different -Dm3plugin.lib setting. On the remote slave the /data/builder/node/workspace/my-job/2.0.3 does not exist. I also created this issue on Jenkins-ci (see https://issues.jenkins-ci.org/browse/JENKINS-10259) I think this is really a plugin problem.
    via by Ivar Kanters,
    • java.io.FileNotFoundException: /data/builder
    • ode/workspace/my-job/2.0.2 at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.loadGlob(ConfigurationParser.java:336) at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:247) at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:135) at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:132) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:106) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:63)
    No Bugmate found.