Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <548717604.1238102262863.JavaMail.jira@brutus>
Date: Thu, 26 Mar 2009 14:17:42 -0700 (PDT)
From: "ying (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2183) Master/slave out of sync with multiple
 consumers of a VirtualTopic on the same broker
In-Reply-To: <1441079828.1238008724046.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

ying updated AMQ-2183:
----------------------

    Attachment:     (was: ActiveMQMessageAuditWithDestination.java)

> Master/slave out of sync with multiple consumers of a VirtualTopic on the same broker
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-2183
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2183
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>         Environment: solaris 10
>            Reporter: ying
>            Priority: Blocker
>             Fix For: 5.3.0
>
>
> 1. producer of VirtualTopic.testTopic publish message to brokerA
> 2. consumer 1 on brokerB with "Consumer.A.VirtualTopic.testTopic
>     consumer 2 on brokerB with "Consumer.A2.VirtualTopic.testTopic
> 3. brokerA and brokerB are bridged.
> Result: you will get 
> ERROR MasterBroker - Slave Failed
> javax.jms.JMSException: Slave broker out of sync with master - Message: ID:yhe-1337-1236273055924-0:16:1:1:738 on queue does not exist among pending(0) for subscription: ID:yhe-3603-1236271682179-0:13:1:1
> Reason:
> In TransactionBroker.java there is a ActiveMQMessageAudit and it will be configured if the broker is a slave. ActiveMQMessageAudit is using the messageId alone to check whether the message is a duplicate. The message for consumer2 will be ignored as duplicate and not saved to the message store because consumer1's same message arrives early.

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