此内容没有您所选择的语言版本。

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
Copy to Clipboard Toggle word wrap
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:
Expand
Object TypeOld ObjectNameNew ObjectNamed
BrokerType=Brokertype=Broker
DestinationType=Queue|Topic,Destination=<destination identifier>type=Broker,destinationType=Queue|Topic,destinationName=<destination identifier>
ConnectorType=Connectortype=Broker,connector=clientConnectors
NetworkConnectorType=NetworkConnectortype=Broker,connector=networkConnectors
ConnectionType=Connectiontype=Broker,connector=*,connectionViewType=remoteAddress|clientId
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat