Comment 6 for bug 657048
Revision history for this message
| Stuart Rossiter (monsieurrigsby) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The correct fix depends on a full understanding of how jvisualvm actually works.
The --jdkhome option appears to control only the JVM that VisualVM runs in, not the JVM which it monitors for Java instances. I can run the Sun VisualVM with the Sun JVM as jdkhome, and still see/monitor Java programs launched using OpenJDK. Equally, I can run the Sun VisualVM with the OpenJDK JVM as jdkhome, and monitor Java programs launched using Sun or OpenJDK JVMs.
Is the fact I can monitor both because:
a) OpenJDK, as a 'fork' of the Sun JDK, retains run-time compatibility in some way?
b) The VisualVM uses standardised JRE/JDK APIs which all JDKs should support (so I could also view stuff launched using, say, IBM's JVM)?
I assume (b), which would mean that my suggested fix is 'correct', because there is no reason to ever want to run one JDK-supplier's VisualVM using another supplier's JVM.