"I wasn't aware of any reason that the logging config and debugging
techniques described on that page would not work properly with mKahaDB. Can
you please elaborate on the failure you referenced?"
- Added the log4j.properties with the following
log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
log4j.appender.kahadb.file=/myowndirectory/kahadb.log
/data/kahadb.log log4j.appender.kahadb.maxFileSize=1024KB
log4j.appender.kahadb.maxBackupIndex=5 log4j.appender.kahadb.append=true
log4j.appender.kahadb.layout=org.apache.log4j.PatternLayout
log4j.appender.kahadb.layout.ConversionPattern=%d [%-15.15t] %-5p
%-30.30c{1} - %m%n
log4j.logger.org.apache.activemq.store.kahadb.MessageDatabase=TRACE, kahadb
- did not restart the ActiveMQ - rather than waited for 10 minutes or so
- there is no kahadb.log file exist in the directory.
The ActiveMQ version i am using 5.14.4
" Also, Sunil rightly pointed out that the behavior you've described can be
caused by uncommitted transactions. Are transactions in use anywhere, and
if so have you explored the possibility that they might not be getting
committed? "
- What is uncommitted transactions ? Based on mKahaDB with per destination
journal logs , the increasing logs are increasing are the 2 queues mentioned
earlier, i.e. forwarded from topic using VirtualDestination. These queue
are processed by a Node.js stomp client which basically inserting the
message data into a NoSQL database - there is no transactions per say in the
code itself.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
