Trouble with Spring JMX with JBoss 4.0.3

Quote:

---

Originally Posted by costin

What about using setServer along with JMXUtils.locateMBeanServer; smth like (from the tip of my head):

Code:

---

<bean id="jmxExporter" class="org.springframework.jmx.export.MBeanExporter"
        lazy-init="false">
    <property name="server">
      <bean class="org.springframework.jmx.JmxUtils" factory-method="locateMBeanServer">
        <constructor-arg value="myJmxMBeanServerName"/>
      </bean>
    </property>
</bean>

---

---

You can also use a locator from JBoss:

Code:

---

<bean id="jmxExporter" class="org.springframework.jmx.export.MBeanExporter"
        lazy-init="false">
    <property name="server">
      <bean class="org.jboss.mx.util.MBeanServerLocator" factory-method="locateJBoss"/>
    </property>
</bean>

---

http://wiki.jboss.org/wiki/Wiki.jsp?...indMBeanServer

I certainly don't think there is a bug in either codebase related to this. Its simply a case of one set of objects being registed in one MBeanServer and another set inside a second MBeanServer. Spring will try to locate the running MBeanServer but it can only guess at the first MBeanServer it encounters unless you specify an agentId.

Look at MBeanServerFactoryBean for more information on configuring lookup.