Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: core
-
Labels:
-
Environment:Windows Server 2003, JDK 1.6.0_23_64, Jenkins 1.415
-
Similar Issues:
Description
Slaves are connected via JNLP
winstone.ClientSocketException: Failed to write to client
at winstone.ClientOutputStream.write(ClientOutputStream.java:41)
at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)
at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:123)
at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:112)
at net.bull.javamelody.FilterServletOutputStream.write(FilterServletOutputStream.java:70)
at net.bull.javamelody.CounterResponseStream.write(CounterResponseStream.java:83)
at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:410)
at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:241)
at org.kohsuke.stapler.Stapler.service(Stapler.java:149)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:249)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:157)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:131)
at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:82)
at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:52)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:65)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at winstone.ClientOutputStream.write(ClientOutputStream.java:39)
... 55 more
Attachments
Issue Links
- is duplicated by
-
JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
-
- Closed
-
- is related to
-
JENKINS-20074 JellyTagException following log message "org.eclipse.jetty.util.log.JavaUtilLog warn"
-
- Resolved
-
-
JENKINS-18992 rssChangeLog should be limited
-
- Open
-
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Jesse Glick [ jglick ] |
Link |
This issue is related to |
Link |
This issue is duplicated by |
Link |
This issue is related to |
Labels | build-pipeline |
Labels | build-pipeline |
Labels | lts-candidate |
Link | This issue is related to JENKINS-18992 [ JENKINS-18992 ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Labels | lts-candidate | 1.509.4-fixed |
Link |
This issue is related to |
Workflow | JNJira [ 140717 ] | JNJira + In-Review [ 189216 ] |
The exception indicates that the HTTP client has shut down the connection without fully reading the response, which is actually quite normal.
In Jenkins, the code is written such that we simply swallow this exception, but if you are seeing it in console, it must be that someone is catching it and dumping it. I suspect the monitoring plugin is causing this.