P4
jcmd JFR.view and JFR.query introduced a new argument type "JULONG" which should be changed to INT.
DiagnosticCommandMBean provides JMX/MBean access to DiagnosticCommands, aka jcmds, as operations (see https://docs.oracle.com/en/java/javase/22/docs/api/jdk.management/com/sun/management/DiagnosticCommandMBean.html ).
The list of types is not well specified, it's left as "implementation dependent" (see DiagnosticCommandArgumentInfo), so currently apps need to have prior knowledge of the type names.
JFR.view introduced a JULONG although the help states INTEGER. It should use "INT" like other diagnostic commands.
JMC knows more than most apps, probably for historical reasons, but does not interpret a "JULONG" and allow editing of the parameter value.
(Separately, we should try and standardise further. Followup in:
8338603: DiagnosticCommandMBean operations should standardize types for parameters.
)
DiagnosticCommandMBean provides JMX/MBean access to DiagnosticCommands, aka jcmds, as operations (see https://docs.oracle.com/en/java/javase/22/docs/api/jdk.management/com/sun/management/DiagnosticCommandMBean.html ).
The list of types is not well specified, it's left as "implementation dependent" (see DiagnosticCommandArgumentInfo), so currently apps need to have prior knowledge of the type names.
JFR.view introduced a JULONG although the help states INTEGER. It should use "INT" like other diagnostic commands.
JMC knows more than most apps, probably for historical reasons, but does not interpret a "JULONG" and allow editing of the parameter value.
(Separately, we should try and standardise further. Followup in:
8338603: DiagnosticCommandMBean operations should standardize types for parameters.
)
- links to
-
Commit(master)
openjdk/jdk/19b2cee4
-
Review(master)
openjdk/jdk/21021