1.2. Key Migration Issues
activemq-core component
In Apache ActiveMQ version 5.8, the
activemq-core component is no longer available. It has been split up into the following components:
activemq-client activemq-broker activemq-jdbc-store activemq-kahadb-store activemq-leveldb-store
This enables your applications to be more lightweight and modular. For example, a Java client application now requires only the
activemq-client JAR, which is much smaller than the old activemq-core JAR.
If you are using the Apache Maven build system, you must replace the
activemq-core artifact by either the activemq-broker artifact or the activemq-client artifact.
Note
The
activemq-all component (which encapsulates the whole ActiveMQ runtime) is still available.
JMX MBeans renamed
The JMX MBeans exposed by ActiveMQ have been refactored to conform to a hierarchical naming structure. If you have any application code that accesses JMX MBeans, you must re-write your code to use the new
ObjectName values. All MBeans now share the type=Broker attribute (where type now starts with a lowercase t). The mapping from old to new ObjectName values is shown in the following table:
| Object Type | Old ObjectName | New ObjectNamed |
|---|---|---|
Broker | Type=Broker | type=Broker |
Destination | Type=Queue|Topic,Destination=<destination identifier> | type=Broker,destinationType=Queue|Topic,destinationName=<destination identifier> |
Connector | Type=Connector | type=Broker,connector=clientConnectors |
NetworkConnector | Type=NetworkConnector | type=Broker,connector=networkConnectors |
Connection | Type=Connection | type=Broker,connector=*,connectionViewType=remoteAddress|clientId |
