JDK-8265754 : Move suspend/resume API from HandshakeState
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 17
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2021-04-22
  • Updated: 2025-05-23
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.
Other
tbdUnresolved
Related Reports
Relates :  
Description
Investigate where and how to move the API to more suitable place.
Comments
It will have to be tightly coupled to HandshakeState I expect, which to me undermines the utility of having a separate class. But sketch it out and see how it looks.
23-05-2025

[~dholmes] Do you think a more suitable place would be a separate class, say HandshakeSuspender, which would have suspend/resume methods, and a pointer to HandshakeState in order to have access to whatever is needed to execute those?
22-05-2025

I hadn't really started on this as it is somewhat vague - what is the criteria for "suitability" here? These things rarely separate cleanly so you just end up with a different form of "unsuitable".
08-05-2025