Quantcast

[JIRA] (JENKINS-14130) reloading http://host/monitoring several times fast give exception

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14130) reloading http://host/monitoring several times fast give exception

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Components: monitoring
Created: 18/Jun/12 1:22 PM
Description:

it seems when i reload the http://host/monitoring before its done relodaing i get this error in the console

←[0m←[33m18-06-2012 15:15:18 org.kohsuke.stapler.compression.CompressionFilter reportException
WARNING: Untrapped servlet exception
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:119)
at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:112)
at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)
at sun.nio.cs.StreamEncoder.implClose(Unknown Source)
at sun.nio.cs.StreamEncoder.close(Unknown Source)
at java.io.OutputStreamWriter.close(Unknown Source)
at java.io.BufferedWriter.close(Unknown Source)
at net.bull.javamelody.HtmlController.doHtml(HtmlController.java:106)
at net.bull.javamelody.MonitoringController.doCompressedHtml(MonitoringController.java:227)
at net.bull.javamelody.MonitoringController.doReportCore(MonitoringController.java:181)
at net.bull.javamelody.MonitoringController.doReport(MonitoringController.java:169)
at net.bull.javamelody.MonitoringFilter.doMonitoring(MonitoringFilter.java:339)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:166)
at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at winstone.ClientOutputStream.write(ClientOutputStream.java:39)
... 44 more
←[0m18-06-2012 15:16:27 winstone.Logger logInternal

to reproduce simply laod the page and hit F5 several times fast..

Environment: Windows Xp, 1.6.0_30 (64-bit) running it from command line
Project: Jenkins
Labels: plugin
Priority: Minor Minor
Reporter: Jes Struck
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14130) reloading http://host/monitoring several times fast give exception

JIRA noreply@jenkins-ci.org
evernat commented on Bug JENKINS-14130

The exception indicates that the HTTP client has shut down the connection without fully reading the response, which is actually quite normal.

Anyway, going beyond this normal state in this case, the org.kohsuke.stapler.compression.CompressionFilter seems to log this as warning.
There is a system property to change this as you can see here:
https://github.com/stapler/stapler/blob/master/core/src/main/java/org/kohsuke/stapler/compression/CompressionFilter.java

So, I think that if you add a system property with "-Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true" and restart Jenkins, then the exception will be thrown to the caller and not logged by this filter.

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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14130) reloading http://host/monitoring several times fast give exception

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
evernat commented on Bug JENKINS-14130

And is it ok now?
Can we close the issue?

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
Loading...