activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Log files not being cleaned up
Date Wed, 13 Sep 2017 14:02:45 GMT
Have you run the troubleshooting procedures in
What did they indicate?

On Sep 12, 2017 8:27 PM, "Lionel van den Berg" <> wrote:

Hi all,
ActiveMQ 5.14.4 running on Suse enterprise 11 sp4

I'm having trouble with the log files (like db-1.log) not being cleaned up
and after about 6 weeks of running ActiveMQ shuts down because there are
too many files in the directory (I think it was 3000), it cannot be
restarted we think due to a JVM limitation. We use a mix of topics and
queues, we can't guarantee that the consumer from the third party won't be
shutdown for an extended period. We are storing messages for 7 days, or at
least we think we are, I've copied the config further down. Don't assume I
know everything that we are doing with all of the config :). I've read
various posts but I'm not sure still whether there might be a parameter
that I can set that will trigger the cleanup.

It looks similar to this but
the last comment there is that it is resolved in 5.14.3, I'm running 5.14.4
on the server side at least, client libraries we did not change.

Does anyone have any ideas?

    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 -->
      <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="AutomationServerThree" dataDirectory="${}">

              <!-- policy for all topics -->
              <policyEntry topic=">" producerFlowControl="true"
useCache="true" expireMessagesPeriod="86400000" alwaysRetroactive="true">
                  <constantPendingMessageLimitStrategy limit="1000"/>
                <!-- discard expired messages -->
                  <sharedDeadLetterStrategy processExpired="false"/>
              <!-- policy for all queues -->
              <policyEntry queue=">" producerFlowControl="true"
useCache="true" expireMessagesPeriod="86400000">
                  <constantPendingMessageLimitStrategy limit="1000"/>
                <!-- discard expired messages -->
                  <sharedDeadLetterStrategy processExpired="false"/>

            The managementContext is used to configure how ActiveMQ is
exposed in
            JMX. By default, ActiveMQ uses the MBean server that is started
            the JVM. For more information, see:

          <managementContext createConnector="true"/>

            Configure message persistence for the broker. The default
            mechanism is the KahaDB store (identified by the kahaDB tag).
            For more information, see:

          <kahaDB directory="/media/SharedStorage/Binaries/activemq"
              <shared-native-file-locker lockAcquireSleepInterval="5000" />

          The systemUsage controls the maximum amount of space the broker
          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
            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=""
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"/>


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message