-
Bug
-
Resolution: Fixed
-
P3
-
13
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8345651 | 11.0.27-oracle | Ivan Bereziuk | P3 | Resolved | Fixed | b01 |
JDK-8229946 | 11.0.6-oracle | Daniil Titov | P3 | Closed | Won't Fix | |
JDK-8229271 | 11.0.5 | Daniil Titov | P3 | Resolved | Fixed | b03 |
jcmd process name matching seems broken in head.
I have a running wildfly instance:
thomas@mainframe:~$ jcmd
30788 jdk.jcmd/sun.tools.jcmd.JCmd
30266 /shared/projects/wildfly/wildfly-16.0.0.Final/jboss-modules.jar -mp /shared/projects/wildfly/wildfly-16.0.0.Final/modules org.jboss.as.standalone -Djboss.home.dir=/shared/projects/wildfly/wildfly-16.0.0.Final -Djboss.server.base.dir=/shared/projects/wildfly/wildfly-16.0.0.Final/standalone
But I cannot attach to it via name part:
thomas@mainframe:~$ jcmd wildfly VM.version
Could not find any processes matching : 'wildfly'
It used to work. It works with jdk11 jcmd and even older jcmds:
thomas@mainframe:~$ oraclejdk8/bin/jcmd wildfly VM.version
30266:
OpenJDK 64-Bit Server VM version 11.0.3-ea+5-sapmachine
JDK 11.0.3
thomas@mainframe:~$ oraclejdk11/bin/jcmd wildfly VM.version
30266:
OpenJDK 64-Bit Server VM version 11.0.3-ea+5-sapmachine
JDK 11.0.3
Note that I still can attach just fine via pid, it is just cumbersome.
I have a running wildfly instance:
thomas@mainframe:~$ jcmd
30788 jdk.jcmd/sun.tools.jcmd.JCmd
30266 /shared/projects/wildfly/wildfly-16.0.0.Final/jboss-modules.jar -mp /shared/projects/wildfly/wildfly-16.0.0.Final/modules org.jboss.as.standalone -Djboss.home.dir=/shared/projects/wildfly/wildfly-16.0.0.Final -Djboss.server.base.dir=/shared/projects/wildfly/wildfly-16.0.0.Final/standalone
But I cannot attach to it via name part:
thomas@mainframe:~$ jcmd wildfly VM.version
Could not find any processes matching : 'wildfly'
It used to work. It works with jdk11 jcmd and even older jcmds:
thomas@mainframe:~$ oraclejdk8/bin/jcmd wildfly VM.version
30266:
OpenJDK 64-Bit Server VM version 11.0.3-ea+5-sapmachine
JDK 11.0.3
thomas@mainframe:~$ oraclejdk11/bin/jcmd wildfly VM.version
30266:
OpenJDK 64-Bit Server VM version 11.0.3-ea+5-sapmachine
JDK 11.0.3
Note that I still can attach just fine via pid, it is just cumbersome.
- backported by
-
JDK-8229271 jcmd process name matching broken
-
- Resolved
-
-
JDK-8345651 jcmd process name matching broken
-
- Resolved
-
-
JDK-8229946 jcmd process name matching broken
-
- Closed
-
- relates to
-
JDK-8205654 serviceability/dcmd/framework/HelpTest.java timed out
-
- Resolved
-
-
JDK-8219721 jcmd from earlier release will hang attaching to VM with JDK-8215622 applied
-
- Resolved
-