activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: in master slave broker network, networked slave incorrectly bound to other slave
Date Wed, 07 Nov 2012 10:36:59 GMT
please do raise a jira and attach your patch. It would be good to
capture the use case and gauge interest. In the main, the shared
nothing master/slave setup does not get a lot of attention, but that
may be b/c it works fine for most users or b/c most folks use a shared
store or independent brokers for the non persistent case.

On 6 November 2012 21:11, mserrano <martin@attivio.com> wrote:
> Note, when I patch DemandForwardingBridge to setNetworkConnection(true) on
> all BrokerInfo commands received by serviceRemoteCommand and patch
> TransportConnection to not create MasterBroker filters for networked slaves,
> this problem does not occur and things proceed as expected.
>
> I think this should be filed as a bug but would like some advice to that
> effect first.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/in-master-slave-broker-network-networked-slave-incorrectly-bound-to-other-slave-tp4658858p4658864.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
http://redhat.com
http://blog.garytully.com

Mime
View raw message