Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.
<beans xmlns=""
<!-- Allows us to use system properties as variables in this configuration file -->
<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations">
<!-- Allows accessing the server log -->
<bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"
lazy-init="false" scope="singleton"
init-method="start" destroy-method="stop">
The <broker> element is used to configure the ActiveMQ broker.
<broker xmlns="" brokerName="${HOSTNAME}" dataDirectory="${}">
<!-- ##### DESTINATIONS ##### -->
<policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb" maxBrowsePageSize="700">
Allow messages to be replayed back to original broker if there is demand.
Due to ENTMQ-444 you also want to configure a replayDelay that is high enough so that
any outstanding message acks are passed along the network bridge *before* we start
to replay messages (replayDelay="500"). The value of replayDelay is a bit of a guess but
on a decently fast network 500 msecs should be enough to pass on and process all message acks.
Note: JMS clients that use the failover transport to connect to a broker in the mesh
arbitrarily should consider using an initialReconnectDelay on the failover url that is
higher than replayDelay configured in the broker. E.g.
This ensures that the demand subscription for this reconnecting consumer is only created
after replayDelay has elapsed.
If its created before, it may lead to the remote broker skipping message dispatch
to the remote broker and those message would seem to be stuck on the broker despite a consumer
being connected via a networked broker.
See ENTMQ-538 for more details.
<conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true" replayDelay="500" />
<policyEntry topic=">" producerFlowControl="true">
The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:
<constantPendingMessageLimitStrategy limit="1000" />
The managementContext is used to configure how ActiveMQ is exposed in
JMX. By default, ActiveMQ uses the MBean server that is started by
the JVM. For more information, see:
<managementContext createConnector="false" />
<defaultIOExceptionHandler ignoreNoSpaceErrors="false"/>
In a full mesh we want messages to travel freely to any broker
(i.e. messageTTL="-1") but create demand subscription only to the next connected
broker (i.e. consumerTTL="1"). See AMQ-4607.
<networkConnector userName="amq" password="topSecret" uri="dns://broker-amq-mesh:61616/?transportType=tcp&amp;queryInterval=30" messageTTL="-1" consumerTTL="1" />
Configure message persistence for the broker. The default persistence
mechanism is the KahaDB store (identified by the kahaDB tag).
For more information, see:
<kahaDB directory="${}/kahadb" />
<jaasAuthenticationPlugin configuration="activemq" />
The systemUsage controls the maximum amount of space the broker will
use before disabling caching and/or slowing down producers.
For more information, see:
<memoryUsage percentOfJvmHeap="70" />
<storeUsage limit="1gb" />
<tempUsage limit="50 gb" />
The transport connectors expose ActiveMQ over a given protocol to
clients and other brokers. For more information, see:
<transportConnector name="openwire" uri="tcp://;wireFormat.maxFrameSize=104857600" />
<!-- ##### SSL_CONTEXT ##### -->
<!-- destroy the spring context on shutdown to stop jetty -->
<bean xmlns="" class="org.apache.activemq.hooks.SpringContextHook" />
Enable web consoles, REST and Ajax APIs and demos
The web consoles requires by default login, you can disable this in the jetty.xml file
Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
<!-- Do not expose the console or other webapps
<import resource="jetty.xml" />
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.