JDK-8238231 : Custom DatagramSocketImpl's create method not called when with protected constructor
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-01-30
- Updated: 2020-02-10
- Resolved: 2020-02-04
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 15 |
|---|
15 b09Fixed  |
Related Reports
|
Relates :
|
Description
A side-effect of JDK-8236925 is that creating a DatagramSocket with a custom DatagramSocketImpl will not invoke the imp's create method to create the socket. DatagramSocketImpl is very under-specified in this area but long standing behavior has been to create the socket lazily. The protected constructor can't throw SocketException and an unchecked exception would be unexpected.
Comments
|