activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Peng (JIRA)" <>
Subject [jira] [Created] (AMQ-6496) levelDB log files fill up disk on 5.14.0 & 5.14.1 releases
Date Wed, 02 Nov 2016 17:07:58 GMT
Patrick Peng created AMQ-6496:

             Summary: levelDB log files fill up disk on 5.14.0 & 5.14.1 releases
                 Key: AMQ-6496
             Project: ActiveMQ
          Issue Type: Bug
          Components: activemq-leveldb-store
    Affects Versions: 5.14.1, 5.14.0
            Reporter: Patrick Peng

My project is currently running on activemq 5.13.3 with replicated levelDB. After upgraded
to either 5.14.0 or 5.14.1, the message delivery works fine but the levelDB log files didn't
get deleted properly and eventually fill up the disk space in data directory. The issue doesn't
occur on activemq 5.13.4.

The test environment has 1 producer, 1 consumer (with autoAct) and messages subscribed/published
thru VirtualTopic.

here is the activemq.xml
<?xml version="1.0" encoding="UTF-8"?><!--
    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.
--><!-- START SNIPPET: example --><beans xmlns=""
xmlns:xsi="" xsi:schemaLocation="">

        <bean class="org.jasypt.encryption.pbe.config.EnvironmentStringPBEConfig" id="environmentVariablesConfiguration">
                <property name="algorithm" value="PBEWithMD5AndDES"/>
                <property name="passwordEnvName" value="ENCRYPTION_KEY"/>

        <bean class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor" id="configurationEncryptor">
                <property name="config" ref="environmentVariablesConfiguration"/>

        <bean class=""
                <constructor-arg ref="configurationEncryptor"/>
                <property name="location" value="file:${activemq.base}/conf/"/>

   <!-- Allows accessing the server log -->
    <bean class="io.fabric8.insight.log.log4j.Log4jLogQuery" destroy-method="stop" id="logQuery"
init-method="start" lazy-init="false" scope="singleton">

        The <broker> element is used to configure the ActiveMQ broker.
    <broker brokerName="ha" dataDirectory="${}" xmlns="">

                <policyEntry topic="&gt;">
                    <!-- 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:

        <persistenceAdapter><replicatedLevelDB bind="tcp://"
directory="/var/avaya/data/activemq/leveldb" hostname="" replicas="3" sync="local_disk"
zkAddress=",," zkPassword="password"
zkPath="/var/avaya/data/activemq/leveldb-stores" zkSessionTimeout="5s"/></persistenceAdapter>

            The systemUsage controls the maximum amount of space the broker will
            use before disabling caching and/or slowing down producers. For more information,
                    <memoryUsage percentOfJvmHeap="70"/>
                    <storeUsage limit="5 gb"/>
                    <tempUsage limit="2 gb"/>

                    <virtualTopic name="&gt;" prefix="VTConsumer.*.*."/>
            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 -->

            <!-- comment out un-needed ports
            <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"/>
        <transportConnector name="openwire" uri="ssl://;amp;wireFormat.maxFrameSize=104857600&amp;amp;needClientAuth=true&amp;amp;transport.enabledProtocols=TLSv1"/></transportConnectors>

           <sslContext keyStore="/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/vf-zr21Node01Cell/nodes/vf-zr21Node01/key.jks"
keyStorePassword="${cert.passwd}" trustStore="/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/vf-zr21Node01Cell/nodes/vf-zr21Node01/trust.jks"

        <!-- destroy the spring context on shutdown to stop jetty -->
            <bean class="org.apache.activemq.hooks.SpringContextHook" xmlns=""/>


        Enable web consoles, REST and Ajax APIs and demos
        The web consoles requires by default login, you can disable this in the jetty.xml

        Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
    <import resource="jetty.xml"/>

</beans><!-- END SNIPPET: example -->

This message was sent by Atlassian JIRA

View raw message