Hi, Stanley I think that is not true.
the duplex option is use to indicate message transfer direction, though broker A connect with broker B, if you set it, the message can transfer from B to A. my understand is 'networkConnector' need to connect two broker, such as A and B, but you can only input one authentication info, if the broker A and B have different authentication, you will fail it. here I have tow suggestion:a) AMQ should this network connector to authenticate remote broker, if connect itself, don't need authentication info. b) AMQ should provide two authentication info, to use connect two broker, itself and remote broker. how do u think this? On Thu, Oct 16, 2008 at 11:18 PM, Dave Stanley <[EMAIL PROTECTED]> wrote: > If the authorization is different for both ends of the network connector, I > think you would need to remove the duplex="true" > > On Wed, Oct 15, 2008 at 11:46 PM, gui pei <[EMAIL PROTECTED]> wrote: > > > Hi, all > > Here is a problem, does anyone know how to resolve it? > > > > I have two ActiveMQ broker, A and B, A has authorization, But B don't > has. > > > > and A has a connection to B. the configuration is this: > > > > <networkConnector name="amq_B" > uri="static://(tcp://server_B:61616)" > > userName="user" password="password" duplex="true"> > > </networkConnector> > > > > according to Active mq document, you must add authorization info. > > > > this test is ok. > > > > but if B has authorization too, and it is different with A. > > > > I know this connection need authorization A and authorization B, I think > > it's no use authorization info connect itself. How should I config this > > connection? > > > > > > Thanks in advance. > > > > -- > > It's winter now, let's hibernate. > > > -- It's winter now, let's hibernate.
