[
https://issues.apache.org/activemq/browse/AMQ-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krishna updated AMQ-2756:
-------------------------
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.
was:
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.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.
Thank you,
Krishna.
> Persistent DLQ messages are NOT persisting in the DB
> -----------------------------------------------------
>
> Key: AMQ-2756
> URL: https://issues.apache.org/activemq/browse/AMQ-2756
> 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
> Attachments: activemq_mysql.xml, TestDLQ.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
