Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
MIME-Version: 1.0
Sender: tbain98@gmail.com
In-Reply-To: <1463540535328-4712083.post@n4.nabble.com>
References: <1463488556093-4712046.post@n4.nabble.com>
	<CAPVVMa9bAWYPD_Eyu4UJEQw0Awc0jVmhf8-vva0NUKhA_hJ7cg@mail.gmail.com>
	<1463540535328-4712083.post@n4.nabble.com>
Date: Wed, 18 May 2016 06:58:55 -0600
Message-ID: <CAPVVMa_EjKU2Leymu-n9Zxy9JZME8exRbUZ+29jkXqSVnqOieA@mail.gmail.com>
Subject: Re: AMQ 5.13.2 : Kaha DB logs cleanup issue
From: Tim Bain <tbain@alumni.duke.edu>
To: ActiveMQ Users <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c12359291725c05331d6b69
archived-at: Wed, 18 May 2016 12:59:06 -0000

--94eb2c12359291725c05331d6b69
Content-Type: text/plain; charset=UTF-8

You're right, your interpretation is consistent with the documented
example, whereas mine is consistent with the text of the log line.  In that
situation, I always assume the documentation is wrong, but that's just an
assumption.  If you or someone else has time to look at the algorithm and
confirm how it actually works, we can update the wiki.  If not, I'll get to
it when I have time.  In the meantime, you should investigate the
conclusions from both algorithms, since you can't be sure which is correct.

I'd be interested to hear what you see via JMX.

Also every durable subscriber on a topic has a subscription message that
can't be GC'ed, so you're never going to get to zero files.  I think I saw
a recent JIRA enhancement to allow those messages to be replayed (into the
newest file) when there are no messages on the topic.  You might want to
search for that enhancement and confirm whether it's in the version you're
using, and upgrade if not.

Tim
On May 17, 2016 9:38 PM, "Shobhana" <shobhana@quickride.in> wrote:

> Thanks Tim, I did not know that the stats are reset when the broker is
> restarted. I'll check how to use JConsole to view the current status of
> consumers.
>
> Yes, all topics have durable subscribers.
>
> I used the logic mentioned in the example given at
>
> http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
> <
> http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
> >
> to identify the topic that prevents log file from being GCed. Even I was
> confused with the example. I expected "dest:0:J" to be holding messages in
> #86; but since the example said "dest:0:I", I thought the trace log was
> meant for "before" and not "after". Maybe this example can be corrected in
> the AMQ link.
> However, since I was unsure whether the trace log was wrong or the example
> was wrong, I cross-checked for any pending messages in both
> riderride.chat.209 and passengerride.user.1234567890 and found that both
> were 0. Hence I raised this question.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/AMQ-5-13-2-Kaha-DB-logs-cleanup-issue-tp4712046p4712083.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

--94eb2c12359291725c05331d6b69--