JDK-8234796 : Refactor Handshake::execute to take a more complex type than ThreadClosure
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-11-26
- Updated: 2020-12-17
- Resolved: 2019-12-03
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 11 | JDK 14 |
|---|---|
| 11.0.11-oracleFixed | 14 b26Fixed  |
Description
To get the handshake context and make future improvements possible Handshake::execute needs a more complex type than ThreadClosure as input. The more complex type can describe it purpose for logging and in the future support different execution models.
Comments
|