"Not supported for this JVM" when using visualvm under Windows (Linux VM works)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
I try to watch an application running in a Linux Tomcat under OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode). I use a jmx connection to watch that application from a remote host.
In a Linux VM (Debian 10.9), I used visualvm 1.4.2 which installed openjdk11, connected nicely and displayed results. However, screen space and performance are limited, also the version is rather old, so I tried visualvm 2.0.7 under Windows. I tried several JDKs, among them the exact same AdoptOpenjdk the Tomcat application is running on and the 11 which worked under Linux, but I always get "Not supported for this JVM" and no results. I can't change the OpenJDK the target application is running under (and it shouldn't be necessary, since it's proven to be usable, right?) but I can change a lot in the Windows environment. But no jdk I tried (1.8, 11, 16, Open, Adopt...) seems to do the job. I didn't find any hints that you can't use Windows visualvm.exe to debug Linux applications, but could that be a problem? Anything else I could try?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with VisualVM 2.0.7 and visualvm.exe on Windows, connecting through JMX to the Linux Tomcat application running OpenJDK. Compare that setup with VisualVM 1.4.2 on Debian and the listed JDK versions. Done means identifying the compatibility boundary or configuration cause and confirming a supported way to display the remote JVM results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100