[AMQ-6367] Queues are not persisted after broker restart when using different persistence from KahaDB

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 5.11.2
• Component/s: Broker, JDBC, KahaDB

Environment

Fedora 22, 64bit

• Assignee: Unassigned
• Reporter: Angelo Atanasov
• Created: 20/Jul/16 08:59
• Updated: 13/Mar/22 14:16
• Resolved: 13/Mar/22 14:16

Description

Steps to reproduce:
1. Set a postgres jdbcPersistenceAdapter :

—
<persistenceAdapter>
<!-- disable kahaDB persistence -->
<!-- <kahaDB directory="${activemq.data}/kahadb"/> -->
<jdbcPersistenceAdapter dataDirectory="${activemq.base}/activemq-data" dataSource="#postgres-ds" createTablesOnStartup="true"/>
</persistenceAdapter>

—

<bean id="postgres-ds" class="org.postgresql.ds.PGPoolingDataSource" destroy-method="close">
<property name="serverName" value="localhost"/>
<property name="databaseName" value="activemqdb"/>
<property name="portNumber" value="0"/>
<property name="user" value="postgres"/>
<property name="password" value="abcdef123"/>
<property name="dataSourceName" value="postgres"/>
<property name="initialConnections" value="1"/>
<property name="maxConnections" value="10"/>
</bean>

2. Start the broker
3. Go to http://localhost:8161/admin/queues.jsp
4. Create manually a queue with some name
5. The queue has been created and listed
6. Restart the broker (./activemq restart)
7. Go back to http://localhost:8161/admin/queues.jsp
8. The queue disappeared!

Expected behavior:

At point 8. The queue should be listed even after a restart.

------------------------------
When we using the kahaDB persistence there is no such issue. It seems that this only happens when we're using external database persistence such as postgres