-
Type:
Bug
-
Status: Resolved
-
Priority:
P3
-
Resolution: Fixed
-
Affects Version/s: 11.0.5
-
Fix Version/s: 15
-
Component/s: security-libs
-
Subcomponent:
-
Resolved In Build:b21
-
CPU:x86
-
OS:linux
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8245015 | 11.0.9-oracle | Prajwal Kumaraswamy | P3 | Resolved | Fixed | master |
| JDK-8245016 | 8u271 | Prajwal Kumaraswamy | P3 | Resolved | Fixed | master |
A DESCRIPTION OF THE PROBLEM :
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
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
-
-
-
- Resolved
-