Hi, [Disclaimer: I know well that Tomcat 5.0 is obsolete, an update is planned but not possible until later this year, and I don't want to leave the monitoring issues unaddressed until then.]
I use Tomcat 5.0 with Java 6. In Java 6, local JMX access with jconsole is active by default. But when I connect, I only see the VM default MBeans. If I enable remote access (with System property com.sun.management.jmxremote.port=9999), but still connect localy via the Pid, I also see the Catalina and User trees in the MBeans page. Can anyone explain what the difference is? Also, I want to adapt the JmxRemoteLifecycleListener, that is in Tomcat Trunk (http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/mbeans/JmxRemoteLifecycleListener.java), for Tomcat 5. This code has undergone a few changes over time, regarding the usage of a seperate MBeanServer by Tomcat. First version did not account for that at all, intermediate versions configured Ports for both the platform and the separate tomcat MBeanServer. The newest revision then removed this again, with the remark that tomcat uses the platform MBeanServer. Could anyone help me understand this? Has there been a previous code change in Tomcat, that this change in the listener reflects? Or does this cause tomcat to use the platform MBeanServer? And what is the situation in Tomcat 5.0? Which revision of the lifecycle listener is the best one to base a backport for 5.0 on? One more question: the JmxRemoteLifecycleListener seems to be in trunk only, what is the state regarding inclusion in Tomcat 6.0? Thanks for any information Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
