이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 17. JMS Broker


Revision History
5/24/12
Updated to include content about how the broker works in enterprise.
5/28/12
Moved information about creating new brokers in enterprise to the broker documentation.
5/28/12
Hid the management section in enterprise because that content is already in the broker documentation.

Abstract

Red Hat JBoss Fuse supports the deployment of JMS brokers. By default, it deploys an Apache ActiveMQ JMS broker. It includes all of the required bundles to deploy additional Apache ActiveMQ instances by deploying a new broker configuration.

17.1. Working with the Default Broker

Revision History
5/29/12
Added directions for disabling the default the default broker.

Abstract

Red Hat JBoss Fuse starts up with a message broker by default. You can use this broker as it is for your application, or you can update its configuration to suite the needs of your application.

Overview

When you deploy a Red Hat JBoss Fuse instance, whether as a standalone container or as a part of a fabric, the default behavior is for a Apache ActiveMQ instance to be started in the container. The default broker creates an Openwire port that listens on port 61616. The broker remains installed in the container and activates whenever you restart the container.

Broker configuration

The default broker's configuration is controlled by two files:
  • etc/activemq.xml—a standard Apache ActiveMQ configuration file that serves as a template for the default broker's configuration. It contains property place holders, specified using the syntax ${propName}, that allow you to set the values of the actual property using the OSGi Admin service.
  • etc/org.fusesource.mq.fabric.server-default.cfg—the OSGi configuration file that specifies the values for the properties in the broker's template configuration file.
For details on how to edit the default broker's configuration see the JBoss A-MQ documentation.

Broker data

The default broker's data is stored in data/activemq. You can change this location using the config command to change the broker's data property as shown in Example 17.1, “Configuring the Default Broker's Data Directory”.

Example 17.1. Configuring the Default Broker's Data Directory

JBossFuse:karaf@root> config:edit org.fusesource.mq.fabric.server.3e3d0055-1c5f-40e3-987e-024c1fac1c3f
JBossFuse:karaf@root> config:propset data dataStore
JBossFuse:karaf@root> config:exit
Copy to Clipboard Toggle word wrap

Disabling the default broker

If you decide that you don't want to use the default broker, you can disable it by removing it's OSGi configuration file:
  1. From the JBoss Fuse command console, delete the configuration PID using the config:delete command as shown in Example 17.2, “Deleting the Default Broker Configuration”.

    Example 17.2. Deleting the Default Broker Configuration

    JBossFuse:karaf@root> config:delete org.fusesource.mq.fabric.server.xxx
    Copy to Clipboard Toggle word wrap
    xxx is the system generated ID for the broker. You can find this value using the config:list command.
  2. From the system terminal, delete the actual configuration file etc/org.fusesource.mq.fabric.server-default.cfg.
It is important to do both steps. Step 1 removes the broker from the running container and its cached deployment information. Step 2 removes the broker's configuration from the file system and ensures that it will not be automatically reloaded if the container is restarted.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat