From: <ad...@jb...> - 2005-07-15 17:11:22
|
Following up on http://jira.jboss.com/jira/browse/JBAS-1610 The issue is that to start the agent for jconsole "-Dcom.sun.management.jmxremote" we must have JBossJMX in the CLASSPATH rather than having ServerImpl setup the system properties and classloader. We cannot use Sun's MBeanServer because 1) We cannot plugin our UnifiedLoaderRepository 2) It does not do MBean context classloading 3) It is slow for Standard/ModelMBean (see the performance tests in the jmx module) In fact when we did use Sun's MBeanServer in 2.4.x we had to implement performance critical mbeans like the EJBContainer using DynamicMBeans. Other alternatives: 1) Write a listener for MBeanRegistration events that creates proxies from the platform mbean server to the JBoss MBeanServer (a poor man's cascading MBeanServer) 2) Deploy a jmx remote connector in JBoss's MBeanServer and use the remote tab to connect to it from jconsole (including adding the platform XMBeans to JBoss's MBeanServer). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885071#3885071 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885071 |