activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-5398) How do I configure a automatic expiration for DLQ
Date Fri, 17 Oct 2014 02:02:33 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-5398.
-----------------------------
    Resolution: Invalid

Questions should be posted to the users list.

> How do I configure  a automatic expiration for DLQ
> --------------------------------------------------
>
>                 Key: AMQ-5398
>                 URL: https://issues.apache.org/jira/browse/AMQ-5398
>             Project: ActiveMQ
>          Issue Type: Task
>          Components: activemq-pool
>    Affects Versions: 5.3.2
>         Environment: RHEL 5.3
>            Reporter: Gopal Chakravarthy
>
> For the dead letter queue ActiveMQ.DLQ,  I would like to configure a policy whereby messages
in DLQ get deleted after they have resided in DLQ for 5 days.
> I couldnt see how to do it in the documentation.
> My current activemq.xml configuration file is below...how do I modify it for autoexpiring
my DLQ messages after 5 days...
> <!--
>     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
>     http://www.apache.org/licenses/LICENSE-2.0
>     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.
> -->
> <beans
>   xmlns="http://www.springframework.org/schema/beans"
>   xmlns:amq="http://activemq.apache.org/schema/core"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
>   http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
>     <!-- Allows us to use system properties as variables in this configuration file
-->
>     <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>         <property name="locations">
>             <value>file:${activemq.base}/conf/credentials.properties</value>
>         </property>
>     </bean>
>     <!--
>         The <broker> element is used to configure the ActiveMQ broker.
>     -->
>     <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost"
dataDirectory="${activemq.base}/data" destroyApplicationContextOnStop="true">
>         <!--
>                         For better performances use VM cursor and small memory limit.
>  For more information, see:
>             http://activemq.apache.org/message-cursors.html
>             Also, if your producer is "hanging", it's probably due to producer flow control.
>             For more information, see:
>             http://activemq.apache.org/producer-flow-control.html
>         -->
>         <destinationPolicy>
>             <policyMap>
>               <policyEntries>
>                 <policyEntry topic=">" producerFlowControl="false" memoryLimit="1mb"
useCache="false">
>                   <pendingSubscriberPolicy>
>                     <vmCursor />
>                   </pendingSubscriberPolicy>
>                 </policyEntry>
>                 <policyEntry queue=">" producerFlowControl="false" memoryLimit="1mb"
useCache="false">
>                   <!-- Use VM cursor for better latency
>                        For more information, see:
>                        http://activemq.apache.org/message-cursors.html
>                   <pendingQueuePolicy>
>                     <vmQueueCursor/>
>                   </pendingQueuePolicy>
>                   -->
>                   <dispatchPolicy>
>   <roundRobinDispatchPolicy />
>                   </dispatchPolicy>
>                 </policyEntry>
>               </policyEntries>
>             </policyMap>
>         </destinationPolicy>
>         <!--
>             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:
>             http://activemq.apache.org/jmx.html
>         -->
>         <managementContext>
>             <managementContext createConnector="false"/>
>         </managementContext>
>         <!--
>             Configure message persistence for the broker. The default persistence
>             mechanism is the KahaDB store (identified by the kahaDB tag).
>             For more information, see:
>             http://activemq.apache.org/persistence.html
>         -->
>         <persistenceAdapter>
>             <kahaDB directory="${activemq.base}/data/kahadb"
>                     ignoreMissingJournalfiles="true"
>                     checkForCorruptJournalFiles="true"
>                     checksumJournalFiles="true"
>                     journalMaxFileLength="64mb" />
>         </persistenceAdapter>
>           <!--
>             The systemUsage controls the maximum amount of space the broker will
>             use before slowing down producers. For more information, see:
>             http://activemq.apache.org/producer-flow-control.html
>         <systemUsage>
>             <systemUsage>
>                 <memoryUsage>
>                     <memoryUsage limit="20 mb"/>
>                 </memoryUsage>
>                 <storeUsage>
>                     <storeUsage limit="1 gb" name="foo"/>
>                 </storeUsage>
>                 <tempUsage>
>                     <tempUsage limit="100 mb"/>
>                 </tempUsage>
>             </systemUsage>
>         </systemUsage>
>                 -->
>         <!--
>             The transport connectors expose ActiveMQ over a given protocol to
>             clients and other brokers. For more information, see:
>             http://activemq.apache.org/configuring-transports.html
>         -->
>         <transportConnectors>
>             <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/>
>         </transportConnectors>
>     </broker>
>     <!--
>         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"/>
> </beans>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message