javax.management.InstanceNotFoundException exception when you use JMX and inprocess mode
You can monitor a Java™ virtual machine by using Java Management Extensions (JMX) in conjunction with Health Center, however there is one incompatibility issue.
On IBM® SDK, Java Technology Edition, Version
6 and earlier, the -Dcom.sun.management.jmxremote JMX
parameter is required to enable the JMX client to monitor a JVM that
is running on the same machine. If you specify this setting on the Java command line when you start
Health Center in inprocess mode, in other words
by specifying java -Dcom.sun.management.jmxremote -Xhealthcenter:level=inprocess,
the following exception is thrown and Health Center fails to start:
javax.management.InstanceNotFoundException: IBM:type=HCMBeanServer
The -Dcom.sun.management.jmxremote JMX
parameter causes a different MBean server to be launched, which causes
this behavior. To avoid the issue, do not use this JMX parameter in
conjunction with Health Center. From IBM SDK, Java Technology Edition, Version
7 onwards, this JMX parameter is no longer required.For more
information about this change in JMX behaviour, see Local Monitoring and Management in the Oracle
JMX documentation.