1 Reply Latest reply on Dec 23, 2003 2:25 AM by adrian.brock

    Exception Processing ErrorPage - broken pipe

    sophomore

      I have added a custom error page to my application using web.xml:

      <error-page>
      <error-code>404</error-code>
      /error/404.jsp
      </error-page>

      my context-root is /, so this is the correct absolute path to the error page. In fact, the error page displays fine when an unavailable resource is requested, but after I deploy the app, I get the following message in the JBoss console:

      ERROR [Engine] ErrorDispatcherValue [localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.jsp] java.net.SocketException:Broken Pipe

      ...then it prints the stacktrace. I would be completely unaware of the exception if I could not see it on the console -- everything appears to be working as I intended. Any ideas why this is happening, and should I be concerned? Thanks!

        • 1. Exception Processing ErrorPage - broken pipe

          I have added a custom error page to my application using web.xml:

          <error-page>
          <error-code>404</error-code>
          /error/404.jsp
          </error-page>

          my context-root is /, so this is the correct absolute path to the error page. In fact, the error page displays fine when an unavailable resource is requested, but after I deploy the app, I get the following message in the JBoss console:

          ERROR [Engine] ErrorDispatcherValue [localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.jsp] java.net.SocketException:Broken Pipe

          ...then it prints the stacktrace. I would be completely unaware of the exception if I could not see it on the console -- everything appears to be working as I intended. Any ideas why this is happening, and should I be concerned? Thanks!