activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Beausoleil (JIRA)" <>
Subject [jira] Commented: (AMQ-2756) Persistent DLQ messages are NOT persisting in the DB
Date Thu, 02 Sep 2010 02:47:42 GMT


Michael Beausoleil commented on AMQ-2756:

Where can I download version 5.4.1 so I can get this fix?  

If version 5.4.1 is not available yet can you tell me how to get this fix in the 5.3.2 or
5.4.0 version as we are currently using the 5.3.2 version and this will be causing us some


> Persistent  DLQ messages are NOT persisting in the DB
> -----------------------------------------------------
>                 Key: AMQ-2756
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.1, 5.3.2
>         Environment: Windows Xp, Linux 2.6.18 (Red Hat 4.1.2-46)
>            Reporter: Krishna
>             Fix For: 5.4.1
>         Attachments: activemq_mysql.xml,
> 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"
> 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:
> Thank you,
> Krishna. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message