Now the jcmd help command requires the process identification either with process id or the main class name which is unnecessary and confusing:
% /java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd help
Error parsing arguments: No command specified
. . . .
% /java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd help VM.flags
Could not find any processes matching : 'help'
But the command works if the process id is specified:
/java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd 28650 help
28650:
The following commands are available:
JFR.configure
JFR.stop
JFR.start
JFR.dump
JFR.check
VM.log
. . . .
/java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd 28650 help VM.flags
28650:
VM.flags
Print VM flag options and their current values.
. . . .
The tool has to be fixed so that the jcmd help command would work without requiring process id or main class name.
% /java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd help
Error parsing arguments: No command specified
. . . .
% /java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd help VM.flags
Could not find any processes matching : 'help'
But the command works if the process id is specified:
/java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd 28650 help
28650:
The following commands are available:
JFR.configure
JFR.stop
JFR.start
JFR.dump
JFR.check
VM.log
. . . .
/java/re/jdk/9/latest/binaries/linux-x64/bin/jcmd 28650 help VM.flags
28650:
VM.flags
Print VM flag options and their current values.
. . . .
The tool has to be fixed so that the jcmd help command would work without requiring process id or main class name.
- relates to
-
JDK-8204595 Extend jcmd vm selection syntax to allow wildcards.
-
- Closed
-
-
JDK-8177763 Getting an hprof dump via jcmd could benefit from stronger option checking
-
- Closed
-
-
JDK-8195777 Better argument parsing and validation in Diagnostic Commands
-
- Closed
-