activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From atjohnson <>
Subject Discrepancies between persistence implementations (KahaDB and JDBC) Destinations retained upon restart using KahaDB but not JDBC
Date Fri, 03 May 2013 14:17:52 GMT
While testing the different message persistence methods I noticed that after
I added queues to the ActiveMQ broker and restarted the broker, the queues
were retained on restart when I as using KahaDB for my message persistence. 
However, I needed to re-create them again if I used a JDBC connection for my
persistence method.

Is this expected behavior?  
Can this be controlled with a configuration I just have not found?  

I could not find anything specific to these questions; if there is
documentation out there explaining this very issue I would be happy to read
it, I just have not found it.

The core problem I am trying to solve by using ActiveMQ is to have a dynamic
broker which only has queues which are required by the application which is
connected to it.  This application could have three functional that each
require a different queue to consume message from; if one of the functions
is disabled via configuration the queue associated with it is no longer
needed and should be discarded to reduce resources.  I would like not to
have to define the queues in the configuration file and instead let the
application connecting to the broker define what queues should be created.

This gets more complicated when adding in broker security and anonymous
access.  If external applications are connecting to the broker anonymously
and the broker goes down for some reason, then even if the broker comes back
up the queues that application is connecting to are missing until created.

 Any insights or approaches other people have gone through to resolve this
issue would be helpful.

Thank you,

Sample Configuration File:

<beans xmlns=""

	<broker xmlns=""
		brokerName="broker" useJmx="true" useShutdownHook="false"

					<policyEntry topic=">" producerFlowControl="true">
								limit="1000" />
					<policyEntry queue=">" producerFlowControl="true"
            <managementContext createConnector="false"/>

			<jdbcPersistenceAdapter dataSource="#persistenceDataSource" />

					<memoryUsage limit="64 mb" />
					<storeUsage limit="100 gb" />
					<tempUsage limit="50 gb" />

			<transportConnector name="tcp"

	<jee:jndi-lookup id="persistenceDataSource" jndi-name="broker_pool" />



View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message