activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2800) JDBCMessageStore message audit suppresses composite destination and DLQ messages as duplicates
Date Thu, 08 Jul 2010 14:43:52 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-2800.
-----------------------------

    Resolution: Fixed

resolved in r961783

Ack removal from store needs to take destination into account as the same message id exists
for multiple destinations when composite destinations are in use. The ack needs to be specific
as it could (this bug) remove the wrong message.
added test for this case.

> JDBCMessageStore message audit suppresses composite destination and DLQ messages as duplicates
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2800
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2800
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.3.1
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> With the audit enabled, messages send to composite destinations are suppressed as duplicates
so the will not survive a restart. In addition, persistent DLQ messages are suppressed (depending
on the audit depth).
> Disabling the audit on the persistence adapter works around this issue. It is ok to disable
the audit. The audit is needed to close a small window where duplicate message sends can occur
with the non transactional use of the failover: transport. It can happen if a send is in progress
when a failover reconnection occurs back o the same broker (as if there was a temp network
partition) and the send reply is not received. A non transactional client will resend the
message which needs to be suppressed by the audit. Disabling the audit leaves the possibility
of having a duplicate message in the database that will not be dispatched.

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


Mime
View raw message