activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bterhune <bterh...@tripwire.com>
Subject Re: Camel Routing places KahaDB in an unexpected place
Date Mon, 04 Feb 2019 19:49:30 GMT
Using ActiveMQ 5.15.8 now,  I took your advice and put breakpoints around.  

Here is what I found..

1. On startup I hit MessageDatabase.setDirectory() with our customer folder
"/data/activemq/kahadb"
2. KahaDB directories are correct, let some time pass for messages to pass
across broker
3. Shutdown..  (We launcher a broker instance from our Java application)

I hit a breakpoint in BrokerService.createPersistenceAdapter():2503
<https://gitbox.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-broker/src/main/java/org/apache/activemq/broker/BrokerService.java;h=f9cd50fe06920cd642c3d473a5d6713a4e80c866;hb=refs/heads/activemq-5.15.x#l2503>
 

Call Stack of breakpoint

getDataDirectoryFile:1096, BrokerService (org.apache.activemq.broker)
  getBrokerDataDirectory:1101, BrokerService (org.apache.activemq.broker)
  createPersistenceAdapter:2503, BrokerService (org.apache.activemq.broker)
  getPersistenceAdapter:1267, BrokerService (org.apache.activemq.broker)
  getSystemUsage:1179, BrokerService (org.apache.activemq.broker)
  checkMemorySystemUsageLimits:2178, BrokerService
(org.apache.activemq.broker)
  start:611, BrokerService (org.apache.activemq.broker)
  doCompositeConnect:127, VMTransportFactory
(org.apache.activemq.transport.vm)
  compositeConnect:91, TransportFactory (org.apache.activemq.transport)
 * doReconnect:1011, FailoverTransport
(org.apache.activemq.transport.failover)*
  iterate:148, FailoverTransport$2 (org.apache.activemq.transport.failover)
  runTask:133, PooledTaskRunner (org.apache.activemq.thread)
  run:48, PooledTaskRunner$1 (org.apache.activemq.thread)
  runWorker:1149, ThreadPoolExecutor (java.util.concurrent)
  run:624, ThreadPoolExecutor$Worker (java.util.concurrent)
  run:748, Thread (java.lang)

If I had to guess, perhaps our camel connection to another broker is
attempting to re-establish the connection on broker shutdown and this is
causing an empty KahaDB to be created?





--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Mime
View raw message