Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-68615

Suppress Excessive java.io.IOException: Broken pipe ERROR when serving static files

    • 213
    • 4
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

            [JRASERVER-68615] Suppress Excessive java.io.IOException: Broken pipe ERROR when serving static files

            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

            Kind regards,
            michael

            Michael Kornatzki added a comment - 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 Kind regards, michael

            Hello again mkornatzki! One of my Support colleagues reached out to me with regards to your latest support request, I am working with her and we will be giving you any further update in your support request. If there is any relevant information to update here, I will make sure to do so as well.

            Rene C. [Atlassian Support] added a comment - Hello again mkornatzki ! One of my Support colleagues reached out to me with regards to your latest support request, I am working with her and we will be giving you any further update in your support request. If there is any relevant information to update here, I will make sure to do so as well.

            Hello, mkornatzki! I believe your last support request related to this issue was attended by me, nearly a year ago. At that time the main bug report JRASERVER-63503 was still open and pending action and there was not much to do from Support side. As of today, the bug report was closed since the fix in this feature request was applied, but if this issue is still affecting you even after upgrading, I suggest raising a new support request, indicating that even with this fix, you still experience the symptoms, and we will be happy to look into it.

            • If you have a more recent support request related to this issue, please add a new comment in it, and refer to my reply here.

            Rene C. [Atlassian Support] added a comment - Hello, mkornatzki ! I believe your last support request related to this issue was attended by me, nearly a year ago. At that time the main bug report JRASERVER-63503 was still open and pending action and there was not much to do from Support side. As of today, the bug report was closed since the fix in this feature request was applied, but if this issue is still affecting you even after upgrading, I suggest raising a new support request, indicating that even with this fix, you still experience the symptoms, and we will be happy to look into it. If you have a more recent support request related to this issue, please add a new comment in it, and refer to my reply here.

            Michael Kornatzki added a comment - - edited

            Well thanks Rene.

            4 Errors consecutively and 136 lines of log is SPAM!

            There is no other one connected to the server, it is s fresh install.

            And the support told me that they can do nothing.

            Michael Kornatzki added a comment - - edited Well thanks Rene. 4 Errors consecutively and 136 lines of log is SPAM! There is no other one connected to the server, it is s fresh install. And the support told me that they can do nothing.

            Hello mkornatzki and a.slomic! Clarifying, the fix applied from this feature request aims to suppress the excessive number of entries for these exceptions, but the error itself can still appear. The idea is to prevent it from flooding the logs. If you are experiencing a behavior where these exceptions are flooding your logs, please raise a support request at https://support.atlassian.com/contact/

            Rene C. [Atlassian Support] added a comment - - edited Hello mkornatzki and a.slomic ! Clarifying, the fix applied from this feature request aims to suppress the excessive number of entries for these exceptions, but the error itself can still appear. The idea is to prevent it from flooding the logs. If you are experiencing a behavior where these exceptions are flooding your logs, please raise a support request at https://support.atlassian.com/contact/

            same here, version 8.1

            Adnan Slomic added a comment - same here, version 8.1

            Still happening in version 8.1

            Michael Kornatzki added a comment - Still happening in version 8.1

            This also happen on version 8

            william@perasotech.com added a comment - This also happen on version 8

            Will this be fixed in the 7.6.* release?

            Al Genzlinger added a comment - Will this be fixed in the 7.6.* release?

            Agree with Sten.  This would be fine, if they had a way of disabling it.  Also, it shouldn't be categorized as an ERROR if there is nothing to act on.  WARNING is far more appropriate

            william@perasotech.com added a comment - Agree with Sten.  This would be fine, if they had a way of disabling it.  Also, it shouldn't be categorized as an ERROR if there is nothing to act on.  WARNING is far more appropriate

              drauf Daniel Rauf
              ddiblasio David Di Blasio
              Votes:
              43 Vote for this issue
              Watchers:
              67 Start watching this issue

                Created:
                Updated:
                Resolved: