You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The servicemix JBIContainer exposes internal services and Components through JMX. The JBIContainer can be passed a JMXBeanServer or be configured to create one, if one doesn't exist. (see Configuration). If the JBIContainer creates its own MBeanServer instance, it also creates an RMI JMXConnector - to allow remote connections. The Ant Tasks use this:

Creating remote JMX Connector to the JBIContainer
String jndiPath = <container name> + "JMX";
JMXServiceURL url = new JMXServiceURL ("service:jmx:rmi:///jndi/rmi://<namingHost>:<namingPort>/" + jndiPath) ;
JMXConnector connector = JMXConnectorFactory.connect(url);


The default namingPort is 1099
The default container name is defaultJBI

Default JMX Service URL

service:jmx:rmi:///jndi/rmi://localhost:1099/defaultJBIJMX

Handy Hint

To enable JMX remoting with Java 5:

export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=5001
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false"


When you want to get at the ServiceMix MBeans using MC4J use JSR160 as your server connection type and the above default JMX Service URL as your server URL.

MC4J - JMX Console

  • No labels