Request for review: 8009650 - HttpClient available() check throws SocketException when connection has been closed (original) (raw)
Dmitry Samersoff dmitry.samersoff at oracle.com
Thu Mar 7 14:00:26 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 ]
Rob,
Is it possible to avoid code duplication?
i.e. do something like this:
int r;
try { ... } catch (SocketException e) { // Comments goes here r = -1 }
if (r == -1){ if (logger. ... available = false; }
return available;
-Dmitry
On 2013-03-07 20:18, 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
-- Dmitry Samersoff Oracle Java development team, Saint Petersburg, Russia
- Give Rabbit time, and he'll always get the answer
- 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 ]