Hello Tim.
Thanks for the hint about the XA transactions.
There were indeed 2 XA transactions hanging in the kahaDB files. After I
committed them via JConsole the store was cleaned-up.
Joachim
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On 03/09/2018 11:26 PM, Tim Bain wrote:
Joachim,
There must have been at least one file that was kept not because of acks in
an earlier file. Presumably this would be the one with the lowest number.
Can you provide the log output for that file?
The standard guess when people say that their
Joachim,
There must have been at least one file that was kept not because of acks in
an earlier file. Presumably this would be the one with the lowest number.
Can you provide the log output for that file?
The standard guess when people say that their KahaDB files are being kept
even though there
Hello.
Recently we had a problem on a ActiveMQ 5.10 version (with manually applied
patch for AMQ-5542).
The mKahaDB data store increased to ~30 GB and couldn´t clean up the data
files anymore.
The log showed always something like this:
/not removing data file: 317633 as contained ack(s) refer to
