Come catturare e ignorare org.apache.catalina.connector.ClientAbortException

Question

Voglio prendere e ignorare il seguente tomcat ClientAbortException. Poiché non è necessario prestare attenzione a ciò per il mio programma.

Qualche idea su come e dove posso rilevare questa eccezione? Sotto è l'eccezione:

14:46:43.920 [ajp-bio-8029-exec-538] ERROR com.sok.runway.URLFilter - Exception in URLFilter 
org.apache.catalina.connector.ClientAbortException: null 
     at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:388) ~[catalina.jar:7.0.26] 
     at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462) ~[tomcat-coyote.jar:7.0.26] 
     at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:366) ~[tomcat-coyote.jar:7.0.26] 
     at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:413) ~[catalina.jar:7.0.26] 
     at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:401) ~[catalina.jar:7.0.26] 
     at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:91) ~[catalina.jar:7.0.26] 
     at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:2031) ~[catalina.jar:7.0.26] 
     at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1870) ~[catalina.jar:7.0.26] 
     at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:958) ~[catalina.jar:7.0.26] 
     at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:411) ~[catalina.jar:7.0.26] 
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:621) ~[servlet-api.jar:na] 
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) ~[servlet-api.jar:na] 
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) [catalina.jar:7.0.26] 
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) [catalina.jar:7.0.26] 
     at com.sok.runway.URLFilter.doFilter(URLFilter.java:130) ~[runway-dev.jar:na] 
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) [catalina.jar:7.0.26] 
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) [catalina.jar:7.0.26] 
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) [catalina.jar:7.0.26] 
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) [catalina.jar:7.0.26] 
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) [catalina.jar:7.0.26] 
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) [catalina.jar:7.0.26] 
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) [catalina.jar:7.0.26] 
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) [catalina.jar:7.0.26] 
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) [catalina.jar:7.0.26] 
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) [catalina.jar:7.0.26] 
     at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200) [tomcat-coyote.jar:7.0.26] 
     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579) [tomcat-coyote.jar:7.0.26] 
     at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:307) [tomcat-coyote.jar:7.0.26] 
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.7.0_03] 
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.7.0_03] 
     at java.lang.Thread.run(Thread.java:722) [na:1.7.0_03] 
Caused by: java.net.SocketException: Connection reset 
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) ~[na:1.7.0_03] 
     at java.net.SocketOutputStream.write(SocketOutputStream.java:153) ~[na:1.7.0_03] 
     at org.apache.coyote.ajp.AjpProcessor.output(AjpProcessor.java:295) [tomcat-coyote.jar:7.0.26] 
     at org.apache.coyote.ajp.AbstractAjpProcessor$SocketOutputBuffer.doWrite(AbstractAjpProcessor.java:1082) ~[tomcat-coyote.jar:7.0.26] 
     at org.apache.coyote.Response.doWrite(Response.java:533) ~[tomcat-coyote.jar:7.0.26] 
     at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:383) ~[catalina.jar:7.0.26] 

Answer 1

dal momento che probabilmente non si vuole una dipendenza a Catalina, è possibile ignorare l'eccezione come questo (sto assumendo la ClientAbortException è la causa):

String simpleName = e.getCause().getClass().getSimpleName(); 
if (simpleName.equals("ClientAbortException")) { 
    // ignore 
} else { 
    // do whatever you do 
} 

Answer 2

ClientAbortException estende IOException. Si può provare il codice sottostante per intercettare l'eccezione:

try { 
    // codes 
    out.write("xyz"); // throws IOException 
} catch (org.apache.catalina.connector.ClientAbortException ca) { 
    System.out.println("ClientAbortException caught"); 
} catch (IOException ioe) { 
    System.out.println("i/o exception raised. abrorting."); 
} 

Answer 3

Nella primavera 4, lo inseriresti in una classe annotata con @ControllerAdvice. Il trucco è quello di sopprimere solo ClientAbortException consentendo ogni altro IOException da trattare come errori o registrati, senza introdurre una dipendenza di compilazione/runtime sul contenitore API:

import java.io.IOException; 
import java.util.logging.Level; 
import java.util.logging.Logger; 

//import org.apache.catalina.connector.ClientAbortException; // We don't want this dependency. 
import org.springframework.web.bind.annotation.ControllerAdvice; 
import org.springframework.web.bind.annotation.ExceptionHandler; 
import org.springframework.web.servlet.NoHandlerFoundException; 

@ControllerAdvice 
public final class ErrorController 
{ 
    @ExceptionHandler(NoHandlerFoundException.class) 
    public String handleNoHandlerFoundException(final NoHandlerFoundException ex) 
    { 
     return "notFoundPage"; 
    } 

    @ExceptionHandler(IOException.class) 
    public String handleAbortedConnection(final IOException ex) 
    { 
     // avoids compile/runtime dependency by using class name 
     if (ex.getClass().getName().equals("org.apache.catalina.connector.ClientAbortException")) 
     { 
      return null; 
     } 

     // log and return error page for any other IOExceptions 
     if (LOGGER.isLoggable(Level.WARNING)) 
     { 
      LOGGER.log(Level.WARNING, "IO Error", ex); 
     } 

     return "errorPage"; 
    } 

    @ExceptionHandler(Exception.class) 
    public String handleException(final Exception ex) 
    { 
     if (LOGGER.isLoggable(Level.SEVERE)) 
     { 
      LOGGER.log(Level.SEVERE, "Server Error", ex); 
     } 
     return "errorPage"; 
    } 
} 

Grazie a questa risposta per fornire il pezzo mancante dove siamo return null for the view name to avoid throwing a SocketException on the closed OutputStream.