[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset"
Senthil Kumar Chandran commented on JENKINS-21541 After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset" I dont see this remoting-2.33.jar in /tmp directory. FYI, I'm still using 1.532 and i didnt upgrade it yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset"
Aaron Digulla commented on JENKINS-21541 After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset" When this happens, can you check whether /tmp/jetty-0.0.0.0-8080-jenkins.war-any/webapp/WEB-INF/lib/remoting-2.33.jar exists? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset"
Senthil Kumar Chandran commented on JENKINS-21541 After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset" Thanks for the updates. I've just tried the same but the issue persists so i've planned to downgrade from 1.547 to 1.532 and currently this issue doesnt appear for me. Not sure whether this issue is with newer version. Any other clue or can u try 1.532 and confirm? Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset"
Thomas Suckow commented on JENKINS-21541 After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset" I've seen this a few times lately, even after 1.549. It always seems to resolve itself if I restart Jenkins. Workaround: 1. Click "Manage Jenkins" 2. Click "Manage Plugins" 3. Click "Download now and install after restart" 4. Check the "Restart Jenkins [...]" box This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset"
Senthil Kumar Chandran commented on JENKINS-21541 After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset" Can anyone help me on this please.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset"
Senthil Kumar Chandran created JENKINS-21541 After I upgrade to 1.547, Maven Build fails with "ERROR: Failed to parse POMs java.net.SocketException: Connection reset" Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Jenkins_Image.JPG Components: maven Created: 29/Jan/14 7:19 AM Description: Recently, i've upgraded the Jenkins from 1.532 to 1.547, but after upgradation, Maven build alone fails with the following reason, if i restart the Jenkins, build is getting succeeded but it fails after some time (say fails after 5 hours) and also some of the image is not visible (attached screenshot) /eas/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/eas/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /eas/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/3.0.4 /tmp/jetty-0.0.0.0-8080-jenkins.war-any/webapp/WEB-INF/lib/remoting-2.33.jar /eas/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar /eas/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar 51932 Exception in thread "main" java.lang.ClassNotFoundException: hudson.remoting.Launcher at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:135) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:64) ERROR: Failed to parse POMs java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:133) at hudson.remoting.Channel.(Channel.java:406) at hudson.remoting.Channel.(Channel.java:402) at hudson.remoting.Channel.(Channel.java:363) at hudson.remoting.Channel.(Channel.java:359) at hudson.remoting.Channel.(Channel.java:355) at hudson.slaves.Channels$1.(Channels.java:71) at hudson.slaves.Channels.forProcess(Channels.java:71) at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:253) at hudson.maven.ProcessCache.get(ProcessCache.java:235) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:749) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1678) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Archiving artifacts Finished: FAILURE Due Date: 29/Jan/14 12:00 AM Environment: Maven 2, Project: Jenkins Labels: jenkins Priority: Major Reporter: Senthil Kumar Chandran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You
