5.8 Migration Guide
There are some changes in 5.8 that may require some code change
- New modules may effect your maven pom dependencies
activemq-corehas been replaced with
activemq-broker. The various message stores have their own activemq-xx-store module. The uber module
Changed JMX Mbean ObjectNames will effect scripts or tools that directly reference Mbean names
All mbeans now share the type=Broker attribute, which gives them containment. In this way, consumers hang off of destinations, which hang off the broker.
The different Mbean types are identified by the presence of specific identifiers in their ObjectNames. The mapping from old to new ObjectName is as follows:
Type|Old Name|New Name ---|---|--- 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
- OSGi integration has changed. The full details are at OSGi Integration. In summary:
- There is a single uber OSGI bundle
- The broker and webconsole are now configured via config admin pid files through an OSGi managed service factory.
- The ActiveMQ binary file
bin/run.jarhas been renamed to