M
Michael Jacobs
Guest
Bart, The ClientAbortException is thrown by the internals of the Tomcat HTTP1.1 engine when it encounters an Java I/O exception writing the HTTP response to the client. That appears to be the case based on the SocketException you showed. So the TCP connection between your WebClient and the Tomcat Connector must be getting closed. Not sure if this is the problem, but the Tomcat connector has an attribute "keepAliveTimeout" which is to detect idle TCP client connections and disconnect the TCP connection. You can try increasing this value (or set -1 to disable it completely) and see if it changes the behavior or not. Mike J.
Continue reading...
Continue reading...