[
https://issues.apache.org/jira/browse/AMQ-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048820#comment-15048820
]
Christopher L. Shannon edited comment on AMQ-6076 at 12/9/15 3:33 PM:
----------------------------------------------------------------------
Since you didn't post your full configuration I'm going to take a guess that
this is happening because you didn't set names for your brokers. You can set a
broker name for each of your brokers as shown in the sample xml here:
http://activemq.apache.org/networks-of-brokers.html
If you need more help you can email the
[users|http://activemq.apache.org/mailing-lists.html] list.
If you think there is a bug somewhere then you can reopen the issue, preferably
with a test case or some more information to track down the problem.
was (Author: christopher.l.shannon):
Since you didn't post your full configuration I'm going to take a guess that
this is happening becauseyou didn't set names for your brokers. if you don't
set up a unique broker name for each broker. You can set a broker name for
each of your brokers as shown in the sample xml here:
http://activemq.apache.org/networks-of-brokers.html
If you need more help you can email the
[users|http://activemq.apache.org/mailing-lists.html] list.
If you think there is a bug somewhere then you can reopen the issue, preferably
with a test case or some more information to track down the problem.
> [DISCUSS] How to solve the problem of two ActiveMQ synchronous exception?
> -------------------------------------------------------------------------
>
> Key: AMQ-6076
> URL: https://issues.apache.org/jira/browse/AMQ-6076
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-camel
> Affects Versions: 5.12.1
> Environment: Configuration：
> <networkConnectors>
> <networkConnector uri="multicast://default" userName="admin"
> password="admin"/>
> </networkConnectors>
> <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"
> discoveryUri="multicast://default" />
> Reporter: chenkw
>
> MQ1:
> INFO | jvm 1 | 2015/11/30 20:33:26 | INFO | Establishing network
> connection from vm://localhost?async=false to tcp://MQ-3:61616
> INFO | jvm 1 | 2015/11/30 20:33:26 | WARN | Failed to add Connection
> localhost->ITP_MQ3-64055-1448551657492-114804:1 due to
> javax.jms.InvalidClientIDException: Broker: localhost - Client:
> NC_ITP_MQ3_inbound_localhost already connected from vm://localhost#0
> INFO | jvm 1 | 2015/11/30 20:33:26 | INFO | Network connection between
> vm://localhost#109468 and tcp://MQ-3/192.168.200.35:61616@57666 shutdown due
> to a local error: javax.jms.InvalidClientIDException: Broker: localhost -
> Client: NC_ITP_MQ3_inbound_localhost already connected from vm://localhost#0
> INFO | jvm 1 | 2015/11/30 20:33:26 | INFO | localhost bridge to ITP_MQ3
> stopped
> INFO | jvm 1 | 2015/11/30 20:33:32 | INFO | Establishing network
> connection from vm://localhost?async=false to tcp://MQ-3:61616
> INFO | jvm 1 | 2015/11/30 20:33:32 | WARN | Failed to add Connection
> localhost->ITP_MQ3-64055-1448551657492-114806:1 due to
> javax.jms.InvalidClientIDException: Broker: localhost - Client:
> NC_ITP_MQ3_inbound_localhost already connected from vm://localhost#0
> INFO | jvm 1 | 2015/11/30 20:33:32 | INFO | Network connection between
> vm://localhost#109470 and tcp://MQ-3/192.168.200.35:61616@57667 shutdown due
> to a local error: javax.jms.InvalidClientIDException: Broker: localhost -
> Client: NC_ITP_MQ3_inbound_localhost already connected from vm://localhost#0
> INFO | jvm 1 | 2015/11/30 20:33:32 | INFO | localhost bridge to ITP_MQ3
> stopped
> MQ3:
> INFO | jvm 1 | 2015/11/30 18:58:53 | INFO | Establishing network
> connection from vm://ITP_MQ3?async=false to tcp://MQ-1:61616
> INFO | jvm 1 | 2015/11/30 18:58:53 | WARN | Failed to add Connection
> ITP_MQ3->localhost-65195-1448550819638-112421:1 due to
> javax.jms.InvalidClientIDException: Broker: ITP_MQ3 - Client:
> NC_localhost_inbound_ITP_MQ3 already connected from vm://ITP_MQ3#2
> INFO | jvm 1 | 2015/11/30 18:58:53 | INFO | Network connection between
> vm://ITP_MQ3#107218 and tcp://MQ-1/192.168.200.13:61616@57199 shutdown due to
> a local error: javax.jms.InvalidClientIDException: Broker: ITP_MQ3 - Client:
> NC_localhost_inbound_ITP_MQ3 already connected from vm://ITP_MQ3#2
> INFO | jvm 1 | 2015/11/30 18:58:53 | INFO | ITP_MQ3 bridge to localhost
> stopped
> INFO | jvm 1 | 2015/11/30 18:58:58 | INFO | Establishing network
> connection from vm://ITP_MQ3?async=false to tcp://MQ-1:61616
> INFO | jvm 1 | 2015/11/30 18:58:58 | WARN | Failed to add Connection
> ITP_MQ3->localhost-65195-1448550819638-112423:1 due to
> javax.jms.InvalidClientIDException: Broker: ITP_MQ3 - Client:
> NC_localhost_inbound_ITP_MQ3 already connected from vm://ITP_MQ3#2
> INFO | jvm 1 | 2015/11/30 18:58:58 | INFO | Network connection between
> vm://ITP_MQ3#107220 and tcp://MQ-1/192.168.200.13:61616@57200 shutdown due to
> a local error: javax.jms.InvalidClientIDException: Broker: ITP_MQ3 - Client:
> NC_localhost_inbound_ITP_MQ3 already connected from vm://ITP_MQ3#2
> INFO | jvm 1 | 2015/11/30 18:58:58 | INFO | ITP_MQ3 bridge to localhost
> stopped
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
