We're coding up special handling for "connection reset by peer" messages in Wicket. Currently ClientAbortException does not override getCause() to return getThrowable(). This makes it difficult for Wicket to safely intercept "connection reset by peer" messages since we cannot catch ClientAbortException (which is Tomcat-specific) and we are forced to parse Exception.getMessage() for "connection reset by peer". This is error-prone because we want to rely as little as possible on the contents of the message -- different JVMs throw different messages sometimes. Can you please try fixing this for the next release?
This has been fixed in 5.5.11.