activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Camel Routing places KahaDB in an unexpected place
Date Sat, 17 Mar 2018 17:00:33 GMT
Can you please provide a reference for what "Camel Routing" is in the
context of ActiveMQ, and how it's a replacement for a network of brokers,
or how Camel would cause the creation of KahaDB content? I've never heard
of either such thing and Google didn't shed any additional light, so as it
stands I have no idea what you're doing and therefore no idea how to help

Also, if we ignore the assertion that Camel is in some way relevant to the
question, you say that "In our activemq.xml configuration we specify the
location of kahaDB
persistence." Can you please provide that portion of your activemq.xml?


On Wed, Mar 14, 2018, 10:45 AM bterhune <> wrote:

> We recently switched our activemq (5.15.2) broker to broker routing from
> using "Network of Brokers" to "Camel Routing" (2.13.0) using Spring XML
> configuration.
> In our activemq.xml configuration we specify the location of kahaDB
> persistence.
> We notice after our product restarts, camel appears to be creating a KahaDB
> instance under the "Current Working Directory".   Based on our current
> deployment requirements this is not desirable.   The directory format is
> <WorkingDir>activemq-data/<brokerName>/KahaDB
> Is there a way to specify a location for this mystery KahaDB we think Camel
> is laying down?
> If this cannot be changed, what is being stored?  Can we assume this is
> routing information and will not grow if our routes are static?
> Thanks, Bob
> --
> Sent from:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message