[crac] RFR: 8378857: [CRaC] Expose checkpoint in CRaCMXBean
Radim Vansa
rvansa at openjdk.org
Fri Feb 27 17:27:44 UTC 2026
On Fri, 27 Feb 2026 17:19:39 GMT, Radim Vansa <rvansa at openjdk.org> wrote:
> As checkpoint is practically a management operation it should be exposed and usable from the MXBean.
>
> In fact the `JDK.checkpoint` operation is already exposed as DiagnosticCommand but this is a better well-known place.
I am not entirely happy about the way how the checkpoint is received on the client - see the RemoteJmxTest. Ideally this could work by the actual checkpoint starting only after the connection is closed from client side; however the JMX (RMI) layer and MBean layers are intentionally separated; while I could register a listener on connection being closed I could not find any way to retrieve the current connection ID in the method. Setting some thread-local for every mbean invocation seems excessive.
I am open to discussion for a better UX, though.
-------------
PR Comment: https://git.openjdk.org/crac/pull/298#issuecomment-3974135086
More information about the crac-dev
mailing list