[
https://issues.apache.org/jira/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063234#comment-13063234
]
Gary Tully edited comment on AMQ-2584 at 7/11/11 9:18 AM:
----------------------------------------------------------
Lars, yes, the audit should be configurable, such that is it possible to
disable. I will expose the option on the default DLQ strategy.
btw: How do you achieve 2), is it a manual process or do you use a camel route
or something else? Any chance you have a test case?
The addition of https://issues.apache.org/jira/browse/AMQ-3003 provides an
alternative way of avoiding duplicate submission to the DLQ in the scenario
described in this issue.
was (Author: gtully):
Lars, yes, the audit should be configurable, such that is it possible to
disable. I will expose the option on the default DLQ strategy.
btw: How do you achieve 2), is it a manual process or do you use a camel route
or something else?
The addition of https://issues.apache.org/jira/browse/AMQ-3003 provides an
alternative way of avoiding duplicate submission to the DLQ in the scenario
described in this issue.
> Massege store is not cleaned when durable topic subscribers are refusing
> messages
> ----------------------------------------------------------------------------------
>
> Key: AMQ-2584
> URL: https://issues.apache.org/jira/browse/AMQ-2584
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.3.0, 5.3.1, 5.4.0
> Environment: WinXP,
> java version "1.6.0_05"
> Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
> Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
> Reporter: Juraj Kuruc
> Assignee: Gary Tully
> Fix For: 5.4.2
>
> Attachments: 2584_test.zip, AMQ2584Test.java, AMQ2584Test.java,
> UpdatedTestCase.patch
>
>
> Hi,
> i am using activemq 5.3 (resp. 5.4 snapshot , 5.3.1 snapshot) with kahadb in
> following use-case:
> - 3 durable topic subscriber, each refuses message using session.recover(), 1
> delivery attempts
> - ActiveMQ.DLQ consumer
> - persistent message topic producer
> In such case deadletter consumer should consume every message sent, as soon
> as number of delivery attempts is reached and mmessage is sent to
> ActiveMQ.DLQ. Result is ok but kahadb data directory at the end contains all
> log files with names db-<number>.log ever created. They aren't deleted even
> after some time.
> I can also see following massege in console:
> WARN | Duplicate message add attempt rejected. Message id:
> ID:sk1d069c-3826-1264006781626
> -0:0:1:1:13425
> If use-case is altered to use queue instead of topic log files are
> periodically deleted without WARN messages in console.
> Same behaviour (data files not cleaned) if amqPersistenceAdapter is used
> except of WARN messages.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
