Request for review: 8009650 - HttpClient available() check throws SocketException when connection has been closed (original) (raw)
Rob McKenna rob.mckenna at oracle.com
Thu Mar 7 08:58:00 PST 2013
- Previous message: Request for review: 8009650 - HttpClient available() check throws SocketException when connection has been closed
- Next message: Request for review: 8009650 - HttpClient available() check throws SocketException when connection has been closed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The outer try/catch is meant to catch potential exceptions originating from the inner try/finally. (from setSoTimeout)
-RobOn 07/03/13 16:51, Kurchi Subhra Hazra wrote:
I am wondering why do you need two try-catch blocks here.
- Kurchi On 3/7/13 8:18 AM, Rob McKenna wrote: Hi folks,
This is a slight alteration of the fix contributed by Stuart Douglas. This fix deals with a SocketException caused by getSoTimeout() on a closed connection. http://cr.openjdk.java.net/~robm/8009650/webrev.01/ -Rob
- Previous message: Request for review: 8009650 - HttpClient available() check throws SocketException when connection has been closed
- Next message: Request for review: 8009650 - HttpClient available() check throws SocketException when connection has been closed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]