Sorry about adding to somebody else's thread I am adding here since I see
same issue in our production server.
We use 5.14.0 version and I have already enabled DLQ to discard all expired
messages and also set expiry of 1 day to all messages (MQTT) and offline
durable consumers using the
KahaDB's data files are not compacted, so a tiny message can keep alive a
32-MB (or whatever size you're using) log file. It's not that the messages
are larger, it's just that lots of clutter gets kept along with the actual
content you're keeping. And if you're not using 5.14.0, then chains of
Thanks for your reply.
> On 27 Sep 2016, at 14:59, Tim Bain wrote:
>
> Do the stats you see in JConsole line up with KahaDBJournalReader (what's
> that?), or with the web console? And do you see an open XA transaction in
> JConsole, like Steve did?
No traces of XA
Do the stats you see in JConsole line up with KahaDBJournalReader (what's
that?), or with the web console? And do you see an open XA transaction in
JConsole, like Steve did?
I'd guess that the negative values indicate that whatever code you
hacked'n'slashed has a bug, either in the code you
I will hijack this thread since I have almost the same problem. Log
files the filling up disk and TRACE telling me:
"not removing data file: XXX as contained ack(s) refer to
referenced file: [XXX]"
Running ActiveMQ 5.13.4.
I hacked'n'slashed KahaDBJournalReader (would be great if the source
code
https://issues.apache.org/jira/browse/AMQ-6440
Tim Bain wrote
> I was going to write a JIRA enhancement request for that when I had some
> free time, but if you have time to write it before I get to it, that would
> be fine. Please put the link here if you do.
>
> On Sep 22, 2016 9:00 AM,
I was going to write a JIRA enhancement request for that when I had some
free time, but if you have time to write it before I get to it, that would
be fine. Please put the link here if you do.
On Sep 22, 2016 9:00 AM, "lichtin" wrote:
> Changing trace levels and using the
Ok, so I hooked up jconsole and looked at the queues, all of the queues
were showing zero. Right underneath the queues there was a section that
said "RecoveredXaTransaction". It had one entry
XID_[1096044365_globalId3132362e392e312e3133392e746. There
really is not very much more
Changing trace levels and using the debugger is not always an option in
production.
I'm wondering why we could not revive the "KahaDBJournalReader" tool
from https://issues.jboss.org/browse/MB-756 and ship it with ActiveMQ.
Tim Bain wrote
> Alternatively, you all could run the KahaDB file
Apparently you can scratch the "but not impossible" bit from my reply.
Thanks Tim, I didn't know it wasn't allowed.
On Sep 22, 2016 7:07 AM, "Tim Bain" wrote:
> Topics will only hold onto messages if 1) a consumer is currently
> connected but hasn't consumed the messages,
Topics will only hold onto messages if 1) a consumer is currently connected
but hasn't consumed the messages, or 2) a consumer subscribed durably but
is now disconnected. #1 indicates a slow (or intentionally misbehaving)
consumer, and isn't likely to be a problem over the span of time you're
On 09/22/2016 08:39 AM, Steve Hill wrote:
After the comment about the TOPIC I decided to take a quick look at
that in the web interface (just to make sure nothing had gone awry)
In deed one of our "queues" had been created as a topic, not sure why
as we use the same code to connect to the
After the comment about the TOPIC I decided to take a quick look at that
in the web interface (just to make sure nothing had gone awry) In deed
one of our "queues" had been created as a topic, not sure why as we use
the same code to connect to the queues however once removed most of the
data
Chris/Tim:
Thanks for the ideas. Unfortunately neither are the case in our situation.
The web client shows 0 messages in any of our queues and we are not using
topics. We did set up the remote debug port and downloaded the source code if
there is anything useful to further troubleshoot
The most likely place for you to have old messages laying around is in the
DLQ. The next most likely place is on a topic for an offline (and never
coming back) durable subscriber.
Tim
On Sep 20, 2016 2:02 PM, "Christopher Shannon" <
christopher.l.shan...@gmail.com> wrote:
Do you have old
Do you have old messages laying around? KahaDB can't clean up old journal
files if there are messages scattered throughout the logs. Even a single
unacked message means that a journal file (and the future files) can't be
cleaned up. This situation tends to happen either when there are old
16 matches
Mail list logo