Re: KAHADB clean up old log files

duction server where I cannot enable trace or JMX. Is there any other way to identify what is causing this issue? TIA, Shobhana -- View this message in context: http://activemq.2283324.n4.nabble.com/KAHADB-clean-up-old-log-files-tp4716661p4717977.html Sent from the ActiveMQ - User

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

-r--. 1 activemq activemq 33554432 Aug 2 01:07 db-918.log >> >>> >> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 3 01:38 db-930.log >> >>> >> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 4 00:19 db-939.log >> >&g

Re: KAHADB clean up old log files

--r--. 1 activemq activemq 33554432 Aug 8 14:00 db-980.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 8 15:41 db-981.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 9 01:43 db-1051.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 11 00:20 db-1066.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 11 03:01 db-1067.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 12 00:19 db-1074.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 12 03:05 db-1075.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 13 00:19 db-1082.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 13 03:04 db-1083.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 14 01:06 db-1093.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 15 01:18 db-.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 16 02:38 db-1126.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 17 00:19 db-1137.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 17 02:32 db-1138.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 18 00:21 db-1155.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 19 00:51 db-1167.log > >>> > >>> -rw-r--r--. 1 activemq activemq 33554432 Sep 19 13:42 db-1277.log > >>> > >>> -rw-r--r--. 1 activemq activemq 597139 Sep 19 14:59 db-1279.log > >>> > >>> Thanks! > >>> > >>> Steve Hill > >>> > >>> ARMADA > >>> > >>> > >>> > >>> > >>> The information contained in this e-mail and any attachments is > >>> confidential and > >>> intended only for the recipient. If you are not the intended recipient, > >>> > >> the > >> > >>> information contained in this message may not be used, copied, or > >>> forwarded to > >>> third parties or otherwise distributed for any other purpose. Please > >>> notify the > >>> sender if you received this e-mail in error and delete the e-mail and > >>> its > >>> attachments promptly. Nothing in this e-mail may be used or deemed to > >>> form the > >>> basis of a contractual or any other legally binding obligation unless > >>> separately > >>> confirmed in writing by an authorized representative of ARMADA. > >>> > >>> > >> > >> > >> > > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/KAHADB-clean-up-old-log-files-tp4716661p4716804.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

32 Aug 12 03:05 db-1075.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 13 00:19 db-1082.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 13 03:04 db-1083.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 14 01:06 db-1093.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 15 01:18 db-.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 16 02:38 db-1126.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 17 00:19 db-1137.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 17 02:32 db-1138.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 18 00:21 db-1155.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Aug 19 00:51 db-1167.log >>> >>> -rw-r--r--. 1 activemq activemq 33554432 Sep 19 13:42 db-1277.log >>> >>> -rw-r--r--. 1 activemq activemq 597139 Sep 19 14:59 db-1279.log >>> >>> Thanks! >>> >>> Steve Hill >>> >>> ARMADA >>> >>> >>> >>> >>> The information contained in this e-mail and any attachments is >>> confidential and >>> intended only for the recipient. If you are not the intended recipient, >>> >> the >> >>> information contained in this message may not be used, copied, or >>> forwarded to >>> third parties or otherwise distributed for any other purpose. Please >>> notify the >>> sender if you received this e-mail in error and delete the e-mail and >>> its >>> attachments promptly. Nothing in this e-mail may be used or deemed to >>> form the >>> basis of a contractual or any other legally binding obligation unless >>> separately >>> confirmed in writing by an authorized representative of ARMADA. >>> >>> >> >> >> -- View this message in context: http://activemq.2283324.n4.nabble.com/KAHADB-clean-up-old-log-files-tp4716661p4716804.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: KAHADB clean up old log files

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,

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

Re: KAHADB clean up old log files

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

KAHADB clean up old log files

Hi fellow ActiveMQ users! I have searched all over the internet and can not find a solution to a problem we are experiencing where old log files are not removed from KAHADB. Needless to say we uncovered this problem when we exceeded the size of our persistent store in production :-) We are