Closed fs111 closed 7 years ago
There could be a couple of problems:
JAVA_HOME
env var is not setJAVA_HOME
does not point to a JDKjvm-mon needs tools.jar to be on the classpath so a quick check is to run stat $JAVA_HOME/lib/tools.jar
@ajermakovics I got the same issue and this is how it looks like the content of my JAVA_HOME
~/t/j/bin ❯❯❯ ls $JAVA_HOME/lib
amd64 visualvm ct.sym ir.idl jconsole.jar orb.idl sa-jdi.jar
missioncontrol ant-javafx.jar dt.jar javafx-mx.jar jexec packager.jar tools.jar
Version:
~/t/j/bin ❯❯❯ java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
MonitorException comes from tools.jar so somehow it is not getting added to the classpath
What if you run it directly:
cd jvm-mon-0.1/
java -cp $JAVA_HOME/lib/tools.jar:lib/jvm-mon-0.1.jar JvmMon
The new version (0.2) will print a warning if tools.jar is not found
The fix to get a valid JAVA_HOME on OS-X is this:
$ export JAVA_HOME=$(/usr/libexec/java_home)
It works now. Thanks!
@ajermakovics worked like a charm, thank you!
When I try to run a build of HEAD, I get the following: