Only with the broker shutdown, of course.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AWS-disk-hosting-ActiveMQ-is-full-UI-purge-delete-doesn-t-work-tp4703991p4704462.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
If you don't need the persisted messages, then go ahead and delete the entire
contents of the kahadb folder, not just the *.log files.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AWS-disk-hosting-ActiveMQ-is-full-UI-purge-delete-doesn-t-work-tp4703991p4704461.html
Sen
Is it okay if I just delete the kahadb (db-1719.log, etc) log files using the
AWS terminal using "rm *.log" in the kahadb directory? I don't need any of
the past data.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AWS-disk-hosting-ActiveMQ-is-full-UI-purge-delete-doesn
Note that the db-#.log files are not general-purpose error logging files,
they are the KahaDB data files.
If KahaDB is holding onto a large number of files, there's a good chance
there are old messages around. The first thing to check is that ActiveMQ is
not being used as a message store. Old me
In addition to what ALi said, look to see if you have any old messages in
the DLQ. That's a classic cause of KahaDB files not getting deleted.
Because KahaDB is a journaling database, I'd be surprised if you can delete
the old messages without giving it at least a little more space, so you
should
configure better the log of kahadb
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
(sorry for double email) first i answer and second i look for info .
On Wed, Nov 18, 2015 at 9:02 AM, ALi wrote:
> if you are seeing so many log ... the problem isnt the kahadb
if you are seeing so many log ... the problem isnt the kahadb store. it is
the size of log you have, and you cant delete logs by the ui
On Tue, Nov 17, 2015 at 5:30 AM, YaoPau wrote:
> Here's what I'm seeing on my AWS box:
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/xvda1 1
Here's what I'm seeing on my AWS box:
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 11G 11G 0 100% /
When I click purge or delete in my ActiveMQ UI, I just get a spinning wheel
that never does anything.
I ssh'd into the AWS box, and I see a number of log files within ka
