Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Date: Tue, 17 May 2016 20:02:15 -0700 (PDT)
From: Shobhana <shobhana@quickride.in>
To: users@activemq.apache.org
Message-ID: <1463540535328-4712083.post@n4.nabble.com>
In-Reply-To: <CAPVVMa9bAWYPD_Eyu4UJEQw0Awc0jVmhf8-vva0NUKhA_hJ7cg@mail.gmail.com>
References: <1463488556093-4712046.post@n4.nabble.com> <CAPVVMa9bAWYPD_Eyu4UJEQw0Awc0jVmhf8-vva0NUKhA_hJ7cg@mail.gmail.com>
Subject: Re: AMQ 5.13.2 : Kaha DB logs cleanup issue
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Wed, 18 May 2016 03:38:21 -0000

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.