activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Updated: (AMQ-2584) Massege store is not cleaned when durable topic subscribers are refusing messages
Date Mon, 16 Aug 2010 16:56:47 GMT


Gary Tully updated AMQ-2584:


junit test case based on submitted test but borrowing from the junit test case attached to

This test case works fine on trunk

> Massege store is not cleaned when durable topic subscribers are refusing messages 
> ----------------------------------------------------------------------------------
>                 Key: AMQ-2584
>                 URL:
>             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
>             Fix For: 5.4.1
>         Attachments:,
> Hi,
> i am using activemq 5.3 (resp. 5.4 snapshot , 5.3.1 snapshot) with kahadb in following
> - 3 durable topic subscriber, each refuses message using session.recover(), 1 delivery
> - 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message