Does the trace actually show each of the log files or only ever some of
them?
Those not listed kahadb cannot be aware of.
James
On 10 June 2011 23:45, Martin C. wrote:
> Hi,
>
> I tried logging and various approaches. I even deleted all queues,
> shut down cleanly via JMX, restarted several ti
Hi,
I tried logging and various approaches. I even deleted all queues,
shut down cleanly via JMX, restarted several times. Except a long
startup for checksumming and verifying the logs, only checkpoint
entries. I even deleted the metadata store in order to force recovery
from the logfile, but stil
I experienced the same. To debug add the following to your log4j.properties
file (if needed):
log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
log4j.appender.kahadb.file=${activemq.base}/data/kahadb.log
log4j.appender.kahadb.maxFileSize=1024KB
log4j.appender.kahadb.maxBackupIndex=5
log4j
enable trace level logging for
org.apache.activemq.store.kahadb.MessageDatabase, this will give
details of the destinations that have references to data files.
If possible, try and make a test case that can reproduce.
On 4 June 2011 19:38, Martin C. wrote:
> Hi,
>
> I experience the problem that
Hi,
I experience the problem that over time my KahaDB storage fills up
despite almost no queue showing pending messages. I upgraded from
ActiveMQ 5.4.2 to 5.5.0 because I thought that according to the change
log these leaks in KahaDB should be fixed in 5.5.0, but for me it
seems they aren't. What
