On Sat, Feb 24, 2018 at 5:11 PM, Rajesh Malla <mallara...@gmail.com> wrote:
> Hello Team
>
> we are connecting n/w connectors
> A->B
> A->C
>
> B->C
> B->A
>
> C->B
> C->A
>
> same broker xml file using to create jcs-brokers, however providing
> different network connector name to each network connector so that we dont
> get invalidclientid exception.
> n/w connector name : A-C, A-B, B-C, B-A, C-D, C-A
>
> surprising thing is :
> in B logs we are seeing
>
> Setting up new connection id:
> jcs-broker->jcs-broker-38993-1519455477826-20:2, address:
> blockingQueue_387166693, info: ConnectionInfo {commandId = 2,
> responseRequired = false, connectionId =
> jcs-broker->jcs-broker-38993-1519455477826-20:2, clientId =
> *replication_3002_C-B_localhost_outbound*, clientIp = null, userName =
> admin, password = *****, brokerPath = null, brokerMasterConnector = false,
> manageable = false, clientMaster = true, faultTolerant = false,
> failoverReconnect = false}
>
Where's the surprising part? Did you include all of the log output that you
intended to post?
> any mistake we are doing ? one observation while creating n/w connector we
> are not providing any queue rules. so this will bridge both queue & topics
> .. is this causing any problem ?
>
> or do we need to specify each broker has specific name ? something we are
> suspecting. please provide suggestions
>
http://activemq.2283324.n4.nabble.com/when-config-network-of-brokers-got-NC-localhost-outbound-err-td2358770.html
seems to indicate that this is necessary, though Bruce's response in
http://activemq.2283324.n4.nabble.com/In-a-network-of-brokers-Are-the-broker-names-required-to-be-different-td3337831.html
doesn't seem to indicate that it's required other than when using multicast
discovery. But it's a recommended practice and it seems straightforward
enough to make this change and see if that eliminates the problem you're
seeing (whatever it is), so I'd do it even if it doesn't fix the problem.
Tim
