Hello Ben,
You are right, Tomcat, with these standard JVM JMX parameters,
creates a new MBeanServer that is not the platform mbean server and
that does not contain the JVM Mbeans (1). I didn't take the time to
figure out wether it was the JVM or Tomcat behavior.
On production, we use Hyp
Hi Cyrille,
Thanks for you reply.
I have actually done what you suggested but that does not relate to the
problem.
To better Illustrate I will give this example:
If I run the code below from a servlet in Tomcat I will get a list of
domains:
String[] domains =
ManagementFactory.getPlatfor
Hello Ben,
Tomcat relies on the out-of-the-box feature of the JVM to make the
MBeanServer accessible to other processes (possibly located on other
servers).
You have to add the following parameters to the Tomcat startup
command line :
-Dcom.sun.management.jmxremote \
-Dcom.sun.ma
Hi,
I use ManagementFactory.getPlatformMBeanServer() from within Apache Tomcat
and from a regular JAR file (outside the scope of apache).
I think (And correct me if im wrong) I'm getting different MBean Servers.
My question is - How Do I reach the Tomcat mbean server from outside or
alternatively,
