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

Alan Conway resolved QPID-4393.
-------------------------------

    Resolution: Fixed

Fixed on trunk 
------------------------------------------------------------------------
r1401710 | aconway | 2012-10-24 10:33:16 -0400 (Wed, 24 Oct 2012) | 9 lines

Bug-869420 - QPID-4393: BrokerReplicator should call queue->bind, not 
exchange->bind

In BrokerReplicator, there are a few places that it calls
exchange->bind(). We're seeing some incorrect behavior during failover testing
(e.g. an exchange shows that it has 5 bindings when there is really only 1) and
we think we've narrowed it down to this. Instead of calling exchange->bind(), it
should call queue->bind(). If you look at qpid::broker::Broker::createObject(),
you'll see that this method calls queue->bind() to bind a queue to an exchange.

------------------------------------------------------------------------

                
> HA BrokerReplicator should call queue->bind, not exchange->bind
> ---------------------------------------------------------------
>
>                 Key: QPID-4393
>                 URL: https://issues.apache.org/jira/browse/QPID-4393
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Clustering
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>
> In BrokerReplicator, there are a few places that it calls exchange->bind().  
> We're seeing some incorrect behavior during failover testing (e.g. an 
> exchange shows that it has 5 bindings when there is really only 1) and we 
> think we've narrowed it down to this.  Instead of calling exchange->bind(), 
> it should call queue->bind().  If you look at 
> qpid::broker::Broker::createObject(), you'll see that this method calls 
> queue->bind() to bind a queue to an exchange.
> (Note that exchange->unbind() appears to be the correct operation for 
> removing a binding, so this shouldn't need to be changed.)

--
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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to