Why Are Empty A-MQ Destinations Removed On Broker Restart ?
Issue
When using the jdbcPersistenceAdapter, empty queues do not persist across broker restarts. This occurs regardless of whether the queues are created by a client app or via the management console. In this particular case, a system administrator is manually creating the queues via the console. The system admin does not have any prior knowledge of what queues will be needed. End user client apps do not have the authority to create destinations; therefore, the destinations are created on-demand via the system admin. It is too burdensome for the system admin to be re-creating those empty queues that do not persist across a broker restart.
Note that this behavior does not occur when using KahaDB; i.e., when using KahaDB, empty queues do persist across broker restarts.
Environment
A-MQ using JDBC persistence adapter.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
