[AMQ-2756] Persistent DLQ messages are NOT persisting in the DB

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3.1, 5.3.2
• Fix Version/s: 5.4.0
• Component/s: Broker

Environment

Windows Xp, Linux 2.6.18 (Red Hat 4.1.2-46)

• Assignee: Gary Tully
• Reporter: Krishna
• Created: 01/Jun/10 21:30
• Updated: 02/Sep/10 07:55
• Resolved: 02/Sep/10 07:55

Description

We are using ActiveMQ 5.3.2 and defined persistence adaptor as below:

<persistenceAdapter>
<jdbcPersistenceAdapter dataSource="#mysql-ds"/>
</persistenceAdapter>

Once the producer sends persistent messages, they are persisting FINE in the 'activemq_msgs' table in the DB (verified by select statement). We also see the messages thru the Web console.

While Consuming, after 6 failure read attempts;
When we check the web Console; the messages are moved from our Queue to "ActiveMQ.DLQ" queue.
BUT when we check the DB, the messages are NOT exist in the 'activemq_msgs' table. They are removed completely. We expect those need to be exist with the container name "queue://ActiveMQ.DLQ".

Since the DLQ messages are not persisted in DB, We are loosing them for Broker restart.

This happens in 5.4-SNAPSHOT & 5.3.1 & 5.3.2 releases.
This works as expected in 5.3.0, i mean, the DLQ messages are persisting in the permanent DB storage.

see this:
http://old.nabble.com/Dead-letter-queue-not-being-created-td28576004.html

Thank you,
Krishna.

Issue Links

• is duplicated by: AMQ-2800 JDBCMessageStore message audit suppresses composite destination and DLQ messages as duplicates