activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Hixson <>
Subject 5.4.0 stops accepting messages randomly
Date Thu, 09 Sep 2010 21:33:16 GMT
We have been running 5.4.0 in production for a few weeks and it can easily handle tens of thousands
of messages a day, but then for no apparent reason it will cease accepting new messages from
our producers.  The consumers will drain the queue empty, but then nothing new gets accepted
into Active MQ.  Restarting Active MQ and then restarting all the producers and consumers
allows things to proceed as normal.
  Below is our activemq.xml.
  Thanks for any help.

    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,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

    <!-- Allows us to use system properties as variables in this configuration file -->
    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="locations">

        The <broker> element is used to configure the ActiveMQ broker. 
    <broker xmlns="" brokerName="localhost" dataDirectory="${activemq.base}/data"
			For better performances use VM cursor and small memory limit.
			For more information, see:
            Also, if your producer is "hanging", it's probably due to producer flow control.
            For more information, see:
                <policyEntry topic=">" producerFlowControl="false" memoryLimit="100mb">
                    <vmCursor />
                <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
                  <!-- Use VM cursor for better latency
                       For more information, see:
            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.base}/data/kahadb"/>
            The systemUsage controls the maximum amount of space the broker will 
            use before slowing down producers. For more information, see:
                    <memoryUsage limit="100 mb"/>
                    <storeUsage limit="10 gb"/>
                    <tempUsage limit="100 mb"/>
            The transport connectors expose ActiveMQ over a given protocol to
            clients and other brokers. For more information, see: 
            <transportConnector name="openwire" uri="tcp://"/>


        Uncomment to enable Camel
        Take a look at activemq-camel.xml for more details
    <import resource="camel.xml"/>

        Enable web consoles, REST and Ajax APIs and demos
        Take a look at activemq-jetty.xml for more details 
    <import resource="jetty.xml"/>
View raw message