activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ying (JIRA)" <>
Subject [jira] Commented: (AMQ-2183) Master/slave out of sync with multiple consumers of a VirtualTopic on the same broker
Date Wed, 22 Jul 2009 13:08:34 GMT


ying commented on AMQ-2183:

hi, Gary,

we have a setup of 4 master/slave broker pair( totally 8 brokers), each pair is a pure master/slave.
All masters are multicast discovered and bridged. However only the master's url are exposed
to the client, we only use slave for data replication. 
in my previous comments, brokerA and brokerB all refers to a master in a network of brokers.
hope this clears things. I will see whether i have time after work to modify the test.

> Master/slave out of sync with multiple consumers of a VirtualTopic on the same broker
> -------------------------------------------------------------------------------------
>                 Key: AMQ-2183
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>         Environment: solaris 10
>            Reporter: ying
>            Assignee: Gary Tully
>            Priority: Blocker
>             Fix For: 5.3.0
>         Attachments:, AMQ-2183.patch
> 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 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.

View raw message