Details
-
Bug
-
Resolution: Fixed
-
P3
-
6u38, 7u40, 8
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8018652 | 7u45 | Robert Mckenna | P3 | Closed | Fixed | b01 |
JDK-8010676 | 7u40 | Robert Mckenna | P3 | Closed | Fixed | b20 |
JDK-8017423 | 6u65 | Robert Mckenna | P3 | Closed | Fixed | b01 |
JDK-8013825 | 6u60 | Robert Mckenna | P3 | Closed | Fixed | b01 |
Description
Unfortunately the fact that the get/setSoTimeout()'s can themselves throw a SocketException was overlooked.
The solution to this problem is to wrap the entire try/catch/finally block (we call setSoTimeout in the finally) in a try/catch (SocketException) which will catch the potential SocketException from the try and finally blocks.
Attachments
Issue Links
- backported by
-
JDK-8010676 HttpClient available() check throws SocketException when connection has been closed
- Closed
-
JDK-8013825 HttpClient available() check throws SocketException when connection has been closed
- Closed
-
JDK-8017423 HttpClient available() check throws SocketException when connection has been closed
- Closed
-
JDK-8018652 HttpClient available() check throws SocketException when connection has been closed
- Closed
- duplicates
-
JDK-8013824 sun.net.www.http.HttpClient#available() does not check server socket closed
- Closed
-
JDK-8019278 sun.net.www.http.HttpClient#available() can throw java.net.SocketException
- Closed
- relates to
-
JDK-7199862 Make sure that a connection is still alive when retrieved from KeepAliveCache in certain cases
- Closed