Servicemix provides JMX based management of running components and the internals of it's container. This section provides infomation about how to connect remotely to the Servicemix MBeanServer, the operations and attributes exposed for management and J2EE statistics.
JMXConsole
JMX Console - infomation about connecting to JMX from an application of management console
MBeans
The following provides infomation on the MBean operation and attributes exposed via JMX within servicemix.
Life Cycle MBean
Component MBean
Container MBean
Environment Context MBean
NMR Broker MBean
Message Flow MBean
Statistics
If ServiceMix is configured (see Configuration) to dump statistics, it will do so for individual JBI components (not lightwight components) in their running directory into the file Stats.csv. Note: for versions prior to v3.1, there is a typo in the filename so .cvs is used instead of .csv, see SM-669. Statistics measure inbound/outbound exchange rates for a component's DeliveryChannel (same information as available in the JMX console). The format of the statistics dumped is:
Info | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
Remote Deployment and Management
The servicemix JBIContainer exposes container, NMR and Component management 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 it's own MBeanServer instance, it also creates an RMI JMXConnector - to allow remote connections. The Management AntTasks use this:
Code Block | ||
---|---|---|
| ||
JMXServiceURL url = new JMXServiceURL ("service:jmx:rmi://<serverHost>/jndi/rmi://<namingHost>:<namingPort>/jmxconnector") ;
JMXConnector connector = JMXConnectorFactory.connect(url);
|
The default namingPort is 1099
...
title | JMX Console |
---|
...