-
Suggestion
-
Resolution: Fixed
-
213
-
4
-
Summary
During our research into JRASERVER-63503 we found the majority occurrences of broken pipe log spamming is occurring when serving static files. An example of what this will look like can be found below:
2018-12-14 09:27:24,247 http-nio-8080-exec-18 ERROR anonymous 567x42x3 1ekan7f 0:0:0:0:0:0:0:1 /s/d41d8cd98f00b204e9800998ecf8427e-T/-anlma9/76012/b6b48b2829824b869586ac216d119363/7aa44fa9aad9a6239c392b1e7bc884f4/_/download/contextbatch/js/browser-metrics-plugin.contrib,-_super,-atl.dashboard,-atl.general/batch.js [o.a.c.c.C.[.[.[.6.10].[file-server]] Servlet.service() for servlet [file-server] threw exception
java.lang.RuntimeException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
at com.atlassian.plugin.cache.filecache.impl.StreamsCache.streamFromFile(StreamsCache.java:113)
at com.atlassian.plugin.cache.filecache.impl.OneStreamCache.stream(OneStreamCache.java:54)
at com.atlassian.plugin.cache.filecache.impl.FileCacheImpl.cache(FileCacheImpl.java:87)
at com.atlassian.plugin.webresource.impl.http.Controller.sendCachedInProduction(Controller.java:319)
at com.atlassian.plugin.webresource.impl.http.Controller.sendCached(Controller.java:282)
at com.atlassian.plugin.webresource.impl.http.Controller.serveResources(Controller.java:222)
at com.atlassian.plugin.webresource.impl.http.Controller.serveBatch(Controller.java:84)
at com.atlassian.plugin.webresource.impl.http.Router$5.apply(Router.java:78)
at com.atlassian.plugin.webresource.impl.http.Router$5.apply(Router.java:71)
at com.atlassian.plugin.webresource.impl.support.http.BaseRouter.callHandler(BaseRouter.java:169)
at com.atlassian.plugin.webresource.impl.support.http.BaseRouter.dispatch(BaseRouter.java:144)
at com.atlassian.plugin.webresource.servlet.PluginResourceDownload.serveFile(PluginResourceDownload.java:65)
at com.atlassian.plugin.servlet.AbstractFileServerServlet.doGet(AbstractFileServerServlet.java:28)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:635)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
... 44 filtered
The purpose of this feature request is to track the progress on suppressing these entries entirely from logging..
- is related to
-
JRASERVER-68617 Logs flooded with "Broken pipe" or other connection errors when using Firefox
-
- Closed
-
- relates to
-
JRASERVER-63503 Frequent java.io.IOException: broken pipe messages appearing in logs
-
- Closed
-
Hello Rene,
thank you.
I use now the "workaround" with the configuration of the log4j.properties to get rid of the messages (
JRASERVER-63503).log4j.logger.org.apache.catalina.connector.ClientAbortException = ERROR, console, cloudAppender log4j.additivity.org.apache.catalina.connector.ClientAbortException = false
But in my opinion the admin didn't have to suppress all the errors![](/images/icons/emoticons/wink.png)
Kind regards,
michael