-
Type:
Bug
-
Status: Closed
-
Priority:
P3
-
Resolution: Fixed
-
Affects Version/s: openjdk8u272, 11.0.5
-
Fix Version/s: 15
-
Component/s: security-libs
-
Subcomponent:
-
Resolved In Build:b21
-
CPU:x86
-
OS:linux
-
Verification:Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8245015 | 11.0.9-oracle | Prajwal Kumaraswamy | P3 | Resolved | Fixed | b01 |
JDK-8249274 | 11.0.9 | Xue-Lei Fan | P3 | Resolved | Fixed | b01 |
JDK-8245016 | 8u271 | Prajwal Kumaraswamy | P3 | Resolved | Fixed | b01 |
JDK-8251714 | emb-8u271 | Prasadarao Koppula | P3 | Resolved | Fixed | team |
We have been setting SO_LINGER to 0 so we can close a secure connection promptly. This has been working well for us in JDK 9 and JDK 10. But it stops working when we move to JDK 11. In JDK 11, it can take 30 seconds to one minute to have a socket really closed (close_notify sent) even with SO_LINGER set to 0.
Comparing source code of JDK 10 and JDK 11, it seems that the SO_LINGER option is ignored in JDK 11.
CUSTOMER SUBMITTED WORKAROUND :
We have done quite some research but can't find a workaround.
FREQUENCY : always
- backported by
-
JDK-8245015 SO_LINGER option is ignored by SSLSocket in JDK 11
-
- Resolved
-
-
JDK-8245016 SO_LINGER option is ignored by SSLSocket in JDK 11
-
- Resolved
-
-
JDK-8249274 SO_LINGER option is ignored by SSLSocket in JDK 11
-
- Resolved
-
-
JDK-8251714 SO_LINGER option is ignored by SSLSocket in JDK 11
-
- Resolved
-
- relates to
-
JDK-8256854 AsyncSSLSocketClose.java has timing issue
-
- Closed
-
-
JDK-8256855 AsyncSSLSocketClose.java has timing issue
-
- Closed
-
-
JDK-8256818 SSLSocket that is never bound or connected leaks socket resources
-
- Resolved
-
-
JDK-8257030 SSL Sockets staying open at the OS level after having been closed
-
- Resolved
-
-
JDK-8224829 AsyncSSLSocketClose.java has timing issue
-
- Closed
-