I did some more research for bug #1237966 and it turns out handling this problem isn't so straight-forward. Tomcat's ClientAbortException makes the classic mistake of defining getThrowable() without overriding getCause() to return that same exception.
As a result, we cannot check for SocketException: connection reset by peer, but rather we now have to check whether *any* exception contains "reset by peer" as a message. I'm not sure how risky this is but I don't see a better way of handling this either. I will continue doing local testing and upload my proposed patch when it's complete.
Gili -- http://www.desktopbeautifier.com/ ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
