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] Updated: (AMQ-2183) Master/slave out of sync with multiple consumers of a VirtualTopic on the same broker
Date Tue, 01 Sep 2009 09:53:24 GMT

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

Gary Tully updated AMQ-2183:
----------------------------

      Component/s: Broker
         Priority: Major  (was: Blocker)
    Fix Version/s:     (was: 5.3.0)
                   5.4.0

pushing this out to 5.4 pending a test case that can demonstrate the problem. Don't think
this can block the 5.3 release, downgrade to major. 

> 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
>          Components: Broker
>    Affects Versions: 5.2.0
>         Environment: solaris 10
>            Reporter: ying
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>         Attachments: ActiveMQMessageAuditWithDestination.java, 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 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.


Mime
View raw message