[ 
https://issues.apache.org/jira/browse/AMQ-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374284#comment-16374284
 ] 

Rajesh Malla commented on AMQ-6075:
-----------------------------------

Can anybody suggest whether there is fix available for this 
InvalidClientIDException ? We are using activemq 5.12.3 version and facing same 
exception.

Can we apply above solution provided by E[~kudi].

Thank you

> javax.jms.InvalidClientIDException: Broker:… already connected
> --------------------------------------------------------------
>
>                 Key: AMQ-6075
>                 URL: https://issues.apache.org/jira/browse/AMQ-6075
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-pool
>    Affects Versions: 5.12.1
>         Environment: OS:Windows Server 2012
>            Reporter: mq
>            Priority: Critical
>
> We have a two node network brokers set up. it can work fine two or three 
> days. Suddenly, every broker will try to create connection to each other, but 
> because 
> There are already has connected to each other, so it will throw a 
> “javax.jms.InvalidClientIDException”.The brokers will retry after 6 second, 
> and the same exception will happened. 
> activemq.log
> 1:02:54,925 | INFO  | Establishing network connection from 
> vm://MQServer1?async=false to tcp://MQServer-2:61618 | 
> org.apache.activemq.network.DiscoveryNetworkConnector | 
> Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector:NC:BrokerService[MQServer1]
> 1:02:55,097 | WARN  | Failed to add Connection 
> MQServer1->MQServer2-123456-123456788990-123:1 due to 
> javax.jms.InvalidClientIDException: Broker: MQServer1 - Client: 
> NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2 | 
> org.apache.activemq.broker.TransportConnection | 
> triggerStartAsyncNetworkBridgeCreation: 
> remoteBroker=tcp://MQServer-2/190.100.100.11:61618@56430, localBroker= 
> vm://MQServer1#4
> 1:02:55,097 | INFO  | Network connection between vm://MQServer1#4 and 
> tcp://MQServer-2/190.100.100.11:61618@56430 shutdown due to a local error: 
> javax.jms.InvalidClientIDException: Broker: MQServer1 - Client: 
> NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2 | 
> org.apache.activemq.network.DemandForwardingBridgeSupport | 
> triggerStartAsyncNetworkBridgeCreation: 
> remoteBroker=tcp://MQServer-2/190.100.100.11:61618@56430, localBroker= 
> vm://MQServer1#4
> 1:02:55,144 | INFO  | MQServer1 bridge to MQServer2 stopped | 
> org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ 
> BrokerService[MQServer1] Task-2043
> wrapper.log
> INFO   | jvm 1    | 1:02:55 |  INFO | Establishing network connection from 
> vm://MQServer1?async=false to tcp://MQServer-2:61618
> INFO   | jvm 1    | 1:02:55 |  WARN | Failed to add Connection 
> MQServer1->MQServer2-123456-123456788990-123:1 due to 
> javax.jms.InvalidClientIDException: Broker: MQServer1 - Client: 
> NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2
> INFO   | jvm 1    | 1:02:55 |  INFO | Network connection between 
> vm://MQServer1#4 and tcp://MQServer-2/190.100.100.11:61618@56430 shutdown due 
> to a local error: javax.jms.InvalidClientIDException: Broker: MQServer1 - 
> Client: NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2
> INFO   | jvm 1    | 1:02:55 |  INFO | MQServer1 bridge to MQServer2 stopped



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to