activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Closed] (AMQ-2810) Pure Master/Slave - Expired messages not replicated to Slave
Date Thu, 29 Nov 2012 21:24:58 GMT


Timothy Bish closed AMQ-2810.

    Resolution: Won't Fix

Pure master/slave removed in upcoming v5.8.0
> Pure Master/Slave - Expired messages not replicated to Slave
> ------------------------------------------------------------
>                 Key: AMQ-2810
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0, 5.3.2
>         Environment: Win32 / Linux64
>            Reporter: Andreas Weber
> I use a Pure Master/Slave configuration with ActiveMQ 5.3.2.
> Master/Slave both use the same DLQ configuration with: processExpired="true" processNonPersistent="true"
> The normal Master/Slave processing seems to work correctly, actions on Master are always
replicated to the Slave.
> But there's a problem: Expired messages do go to the Master's DLQ, but this is not adapted
in the Slave.
> I debugged in the (Slave's) Code and found the appropriate send-to-DLQ-Command/Message
arriving at the MasterConnector.
> But in further processing this message is filtered out as a duplicate(?) (TransactionBroker.send()
resp. ActiveMQMessageAudit.isDuplicate()). It seems that this ProducerSequenceBit, which is
checked there, was already set... but here I'm a little bit lost in the code.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message