6 Replies Latest reply on Feb 3, 2006 6:17 AM by 666705

    Broken Pipe

    3004
      Hello,

      we get often the exception "java.io.IOException: Broken pipe" in our
      logfile.
      I know, we can ignore them, but we dont want the excpetion in our logfile!
      The stacktrace are to big and its not funny to read the logfile with so much
      'broken pipe' exception.
      Is there a way to say bea to ignore the broken pipe exception (dont write it
      to the logfile!).


      ####<15.06.2004 12:19:07 CEST> <Error> <HTTP> <solr-471.srv.mediaways.net>
      <server2> <ExecuteThread: '30' for queue: 'default'> <kernel identity> <>
      <101017> <[ServletContext(id=26
      92217,name=web/dtf,context-path=/dtf)] Root cause of ServletException>
      javax.servlet.jsp.JspException: [ServletException
      in:/tiles/common/profile_template.jsp] [ServletException
      in:/tiles/profile/leftnav.jsp] Input/output error: java.io.IOException: B
      roken pipe''
      at
      org.apache.struts.taglib.tiles.InsertTag$InsertHandler.processException(Inse
      rtTag.java:956)
      at
      org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.ja
      va:905)
      at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:473)
      at
      jsp_servlet._tiles._common.__mainlayout._jspService(__mainlayout.java:1035)
      at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
      at
      weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
      tStubImpl.java:1075)
      at
      weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
      :418)
      at
      weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
      :306)
      at
      weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
      l.java:312)
      at
      org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:10
      69)



      Best regards
      Heiko Priebe

      http://www.heikopriebe.de


        • 1. Re: Broken Pipe
          3004

          Hi,

          I am facing a smilar problem only difference bein that my session gets flushed
          after i get that error.... pls reply

          "H Priebe" <prihei_nospam@web.de> wrote:
          Hello,

          we get often the exception "java.io.IOException: Broken pipe" in our
          logfile.
          I know, we can ignore them, but we dont want the excpetion in our logfile!
          The stacktrace are to big and its not funny to read the logfile with
          so much
          'broken pipe' exception.
          Is there a way to say bea to ignore the broken pipe exception (dont write
          it
          to the logfile!).


          ####<15.06.2004 12:19:07 CEST> <Error> <HTTP> <solr-471.srv.mediaways.net>
          <server2> <ExecuteThread: '30' for queue: 'default'> <kernel identity>
          <>
          <101017> <[ServletContext(id=26
          92217,name=web/dtf,context-path=/dtf)] Root cause of ServletException>
          javax.servlet.jsp.JspException: [ServletException
          in:/tiles/common/profile_template.jsp] [ServletException
          in:/tiles/profile/leftnav.jsp] Input/output error: java.io.IOException:
          B
          roken pipe''
          at
          org.apache.struts.taglib.tiles.InsertTag$InsertHandler.processException(Inse
          rtTag.java:956)
          at
          org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.ja
          va:905)
          at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:473)
          at
          jsp_servlet._tiles._common.__mainlayout._jspService(__mainlayout.java:1035)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at
          weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
          tStubImpl.java:1075)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :418)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :306)
          at
          weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
          l.java:312)
          at
          org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:10
          69)



          Best regards
          Heiko Priebe

          http://www.heikopriebe.de

          • 2. Re: Broken Pipe
            666705
            Hello,
            I get the broken pipe in a JSP when a second request is send before the first request was answered. I catch the Exception, but the session is destroyed. How can I avoid the destroying of the session?

            Thank you, Joern.

            Message was edited by joern at Nov 11, 2004 7:35 AM

            Message was edited by joern at Nov 11, 2004 7:57 AM
            • 3. Re: Broken Pipe
              666705
              We had met similar problem. Because we have background attribute in table tag. Once background attribute was removed from the table tag. The broken pipe is gone.
              • 4. Re: Broken Pipe
                666705
                This problems typically occurs due to a TCP problem.
                You can setup your TCP parameters ( command ndd in Solaris, no in AIX and so on ... )


                Cheers !

                Jin
                • 5. Re: Broken Pipe
                  666705
                  Hi,
                  please check your network connections
                  Prasanna Yalam
                  • 6. Re: Broken Pipe
                    666705
                    Hello,

                    Quite recently we had a lot of Broken Pipe Exceptions being shown in our log files. It was creating a lot of escalations from our client. We get this exception only from a particular set of JSP's and only in Weblogic (we didn't get the exception in Tomcat for same application).

                    We had traced that the Broken pipe is being caused by a
                    <%@ page errorPage="/jsp/JSPErrorPage.jsp" %> tag.

                    Can anybody tell me what caused this?

                    Thanking you,

                    Regards,
                    Leela Manoranjan