[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
hardwickj closed JENKINS-14825 as Duplicate winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 @xu, this issue was closed because it's a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-10524. Please post any comments or further information there instead. Re-closing... Change By: hardwickj (15/May/13 3:13 PM) Status: Reopened Closed Resolution: Duplicate 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] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
xu dong reopened JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 I encounter this problem.On Windows xp X86 SP2 with java version "1.7.0_11", Jenkins ver: 1.488 ,build-pipeline: 1.3.4-snapshot,run by java -jar jenkins.war Change By: xu dong (15/May/13 9:19 AM) Resolution: Duplicate Status: Resolved Reopened 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] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
xu dong edited a comment on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Same here on Windows xp X86 SP2 with java version "1.7.0_11", Jenkins ver: 1.488 ,build-pipeline: 1.3.4-snapshot,run by java -jar jenkins.war 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] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
xu dong commented on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Same here on Windows xp X86 SP2 with java version "1.7.0_11", run by java -jar jenkins.war 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] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
Jesse Glick resolved JENKINS-14825 as Duplicate winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Change By: Jesse Glick (07/May/13 2:54 PM) Status: Open Resolved Resolution: Duplicate 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] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
hardwickj commented on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 We've been seeing this occasionally, and cannot nail it down to a root cause. I've disabled numerous plugins to try and narrow it down, but I'm still unable to find anything that can recreate it consistently. The error seems to result in parts of the web app returning 404. Must be some of the ajax'y portions that make a call out after the initial page load. Unfortunately we also make fairly heavy use of Jenkins API's, and with the API randomly returning a 404 it's severely impacting our workflow. It seems odd to me that the API/UI return a 404 error when in the log we're seeing a straight up exception. I'd expect some sort of 500 error... This is what we see in our logs: May 06, 2013 10:55:13 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/ssd/hudson/war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/summary.jelly:49:48: Failed to write to client at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) ... Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/ssd/hudson/war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/summary.jelly:49:48: Failed to write to client at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) ... Caused by: winstone.ClientSocketException: Failed to write to client at winstone.ClientOutputStream.write(ClientOutputStream.java:41) ... Caused by: java.net.SocketException: Connection reset at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) 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] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
hardwickj updated JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Change By: hardwickj (06/May/13 2:57 PM) Priority: Major Critical 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.
