[
https://issues.apache.org/activemq/browse/AMQ-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies updated AMQ-1797:
----------------------------
Fix Version/s: (was: 5.2.0)
5.3.0
> persistent messages for durable subscribers are not purged from disc storage
> ----------------------------------------------------------------------------
>
> Key: AMQ-1797
> URL: https://issues.apache.org/activemq/browse/AMQ-1797
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.1.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: Rob Davies
> Fix For: 5.3.0
>
> Attachments: Storage_cleanup_Redelivery_test.zip,
> textMessageFile.txt, TopicConsumers.java, TopicProducer.java
>
>
> I have some problems with multiple durable subscribers while persistent
> delivery is used.
> Message should be deleted from disc storage (periodically) after all
> interested subscribers have received it. In case there was one durable
> subscriber everything woks just fine. However when I tested this scenerio
> with two durable subscribers on topic, the messages were never deleted (disc
> usage is continously consumed and never purged).
> Test case description:
> -using default activemq.xml configuration file from binary distribution
> -TopicConsumers.java creates two separetes durable consumers
> -textMessageFile.txt is file which text is sent by producer (place it on
> classpath)
> Result:
> -all messages there were send were also received by both subscribers
> -after more then 100k messages data directory is about 1GB.
> -restarting activemq with so big persistent storage takes very long time
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
