Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 28 Mar 2012 22:49:28 +0000 (UTC)
From: "Timothy Bish (Reopened) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1313897545.30438.1332974968774.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1917501128.32437.1332184898956.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (AMQ-3775) KahaDB journal files retained after
 delay in "unsubscribing" durable subscriber from topic.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish reopened AMQ-3775:
-------------------------------


Found additional cases where this can happen.
                
> KahaDB journal files retained after delay in "unsubscribing" durable subscriber from topic.
> -------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3775
>                 URL: https://issues.apache.org/jira/browse/AMQ-3775
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.5.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.6.0
>
>
> KahaDB journal files retained after delay in "unsubscribing" durable subscriber from topic.This issue only appears to occur when Durable Subscriber is registered with a "selector" that does not match all messages on topic.
> Scenario:
> Msg Producer sending messages to topic.
> Durable subscriber registered with a selector on topic
> After 20 seconds; stop calling consumer.receive() .
> Another Durable subscriber registers on the topic
> After 20 seconds; stop calling consumer.receive() .
> Continue this pattern till 10 durable subscribers are registered with topic
> Then unsubscribe all 10 Durable subscribers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira