So JMXTransAgent is working quite well for my usages. As we are pushing into moving to JDK 1.9; I've tripped upon JDK 1.9's removal of Xbootclasspath in favor of 'patch-module' or something like that.
In the JDK 1.8 era, I've been using some additional JDK_OPTS like so:
export JAVA_OPTS="-Xbootclasspath:/opt/jboss-eap-7.1.0/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.7.Final-redhat-1.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djmxtrans.agent.premain.waitForCustomMBeanServer=true -javaagent:/opt/jmxtrans-agent-1.2.8-SNAPSHOT.jar=/opt/jmxtrans-agent.xml"
So this doesn't work in JDK 1.9. Is there any simple tweak for this? -Xbootclasspath/a , which still seems supported in JDK 1.9, gets same result as if no boot classpath was used (in JDK 1.8, or JDK 1.9) : LogManager not installed.
So JMXTransAgent is working quite well for my usages. As we are pushing into moving to JDK 1.9; I've tripped upon JDK 1.9's removal of Xbootclasspath in favor of 'patch-module' or something like that.
In the JDK 1.8 era, I've been using some additional JDK_OPTS like so:
export JAVA_OPTS="-Xbootclasspath:/opt/jboss-eap-7.1.0/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.7.Final-redhat-1.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djmxtrans.agent.premain.waitForCustomMBeanServer=true -javaagent:/opt/jmxtrans-agent-1.2.8-SNAPSHOT.jar=/opt/jmxtrans-agent.xml"So this doesn't work in JDK 1.9. Is there any simple tweak for this? -Xbootclasspath/a , which still seems supported in JDK 1.9, gets same result as if no boot classpath was used (in JDK 1.8, or JDK 1.9) : LogManager not installed.