2017-03-23 16:35
浏览 119


I do get ActiveMQ supports data persistence (http://activemq.apache.org/persistence.html), but i cannot understand how to make it work, the result is when i restart ActiveMQ all the messages disappear, while queues and topics remain.

I've read about to enable persistence on a database but i want to keep data on the filesystem since my system is facing database perfomance issues.

This is my activemq.xml

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.
<!-- START SNIPPET: example -->

<!-- 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="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}">

            <policyEntry topic=">" >
                <!-- 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"/>

        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="${activemq.data}/kahadb"/>

        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="100 gb"/>
                <tempUsage limit="50 gb"/>

        The transport connectors expose ActiveMQ over a given protocol to
        clients and other brokers. For more information, see:

        <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
        <transportConnector name="openwire" uri="tcp://;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="amqp" uri="amqp://;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="stomp" uri="stomp://;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="mqtt" uri="mqtt://;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="ws" uri="ws://;wireFormat.maxFrameSize=104857600"/>

    <!-- destroy the spring context on shutdown to stop jetty -->
        <bean xmlns="http://www.springframework.org/schema/beans" 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
<import resource="jetty.xml"/>
  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 邀请回答

3条回答 默认 最新

  • doudou0111
    doudou0111 2017-04-03 10:28

    Thanks to all, what i was looking for is to set Quality of Service > 1 for the publisher client, since the default QoS is 0.

    点赞 评论
  • dtjxhf595733
    dtjxhf595733 2017-03-23 17:45

    You need to send messages persistent as well. This is a client side thing to decide. In Java/JMS you would set the DeliveryMode.PERSISTENT while sending messages. In other client frameworks, like MQTT, there are other ways to specify it such as QoS = 1 or 2.

    点赞 评论
  • douguai7291
    douguai7291 2017-03-24 11:22

    In order to enable persistence on the broker you have to choose a persistence adapter. You have done this by specifying in activemq.xml that you want to use KahaDB.

    <broker brokerName="broker" persistent="true" ...>
             <kahaDB directory="${activemq.data}/kahadb"/>

    Ok, now the broker knows that you want to persist the incoming messages, but the client can still override this setting. In order to do that, you need to specify when sending a message that you want it to be persisted. Check what mechanism you are using for sending messages and make sure that they are set to be persisted.

    For e.g. if you use Spring's JmsTemplate for sending messages you would have to call setDeliveryPersistent(...). This is only an example, please note that the default for this method is "true" aka delivery mode "PERSISTENT".

    点赞 评论