[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2020-02-17 Thread ABDELOUHAB MOHAMMED (Jira) 


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

ABDELOUHAB MOHAMMED commented on AMQ-6075:
--

Thanks,

 

The same warning.

http://0.0.0.0:8081?maximumConnections=1000wireFormat.maxFrameSize=104857600;
 allowLinkStealing="true"/>

Thanks.

> javax.jms.InvalidClientIDException: Broker:… already connected
> --
>
> Key: AMQ-6075
> URL: https://issues.apache.org/jira/browse/AMQ-6075
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: 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
(v8.3.4#803005)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2020-02-17 Thread Kim Zeevaarders (Jira) 


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

Kim Zeevaarders commented on AMQ-6075:
--

[~mabdelouhab] i don't know for sure but we have it set like this in the 
broker.xml of the activemq broker:

 
{code:java}
 
{code}
 

> javax.jms.InvalidClientIDException: Broker:… already connected
> --
>
> Key: AMQ-6075
> URL: https://issues.apache.org/jira/browse/AMQ-6075
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: 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
(v8.3.4#803005)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2020-02-17 Thread ABDELOUHAB MOHAMMED (Jira) 


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

ABDELOUHAB MOHAMMED commented on AMQ-6075:
--

Thanks,

 

i have the same warning, with  linkStealing=true and allowLinkStealing=true too:

http://0.0.0.0:8081?maximumConnections=1000allowLinkStealing=truewireFormat.maxFrameSize=104857600"/>

 

thanks.

> javax.jms.InvalidClientIDException: Broker:… already connected
> --
>
> Key: AMQ-6075
> URL: https://issues.apache.org/jira/browse/AMQ-6075
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: 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
(v8.3.4#803005)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2020-02-17 Thread Kim Zeevaarders (Jira) 


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

Kim Zeevaarders commented on AMQ-6075:
--

[~mabdelouhab] we didnt find any functional problems with this exception but it 
flooded our logging from while to while. We managed to prevent the issue when 
setting linkStealing=true on the transportconnector: 
[https://activemq.apache.org/configuring-transports]

 

this is still not a solution (the question remains why the broker want to 
re-add already existing connections), but it seems to do the job for us. 

If someone can tell us if there are downsides to our implemented fix please let 
us know!

> javax.jms.InvalidClientIDException: Broker:… already connected
> --
>
> Key: AMQ-6075
> URL: https://issues.apache.org/jira/browse/AMQ-6075
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: 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
(v8.3.4#803005)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2020-02-17 Thread ABDELOUHAB MOHAMMED (Jira) 


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

ABDELOUHAB MOHAMMED commented on AMQ-6075:
--

i have the same error with the version 5.15.11 and openjdk 8

 

2020-02-17 14:55:05,098 | WARN | Failed to add Connection 
id=ID:-42605-1581514054408-2:120, clientId= due to {} | 
org.apache.activemq.broker.TransportConnection | qtp-210690747-534
javax.jms.InvalidClientIDException: Broker: localhost - Client:  already 
connected from blockingQueue_920727276
 at 
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:247)[activemq-broker-5.15.11.jar:5.15.11]
 at 
org.apache.activemq.broker.jmx.ManagedRegionBroker.addConnection(ManagedRegionBroker.java:227)[activemq-broker-5.15.11.jar:5.15.11]
 at 
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:99)[activemq-broker-5.15.11.jar:5.15.11]

 

i have an http client connection to the broker with the following configuration:

 

http://0.0.0.0:8081?maximumConnections=1000wireFormat.maxFrameSize=104857600"/>

 

 

> javax.jms.InvalidClientIDException: Broker:… already connected
> --
>
> Key: AMQ-6075
> URL: https://issues.apache.org/jira/browse/AMQ-6075
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: 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
(v8.3.4#803005)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2020-01-23 Thread Kim Zeevaarders (Jira) 


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

Kim Zeevaarders commented on AMQ-6075:
--

Hi, 

why was this issue never fixed? We are experiencing the same thing with version 
5.10.2. I can understand that it is no big problem since the connection is 
already there, but why would activemq even try to re-add the connection? 

Can somebody from the developers please confirm this is no real problem? After 
we encounter this warning it seems everything is running fine (no loss of 
service) and we always restart the servers to stop the logging of the warning. 
However, it would be nice to hear from someone what could be the cause and/or 
if this is a real problem...

Regards,

Kim

> javax.jms.InvalidClientIDException: Broker:… already connected
> --
>
> Key: AMQ-6075
> URL: https://issues.apache.org/jira/browse/AMQ-6075
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: 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
(v8.3.4#803005)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2018-02-23 Thread Rajesh Malla (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQ-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2016-01-07 Thread Ehud Kleers (JIRA) 

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

Ehud Kleers commented on AMQ-6075:
--

This exception is thrown from TransportConnection.java, from the function 
processAddConnection():

///
 try {
broker.addConnection(context, info);
} catch (Exception e) {
//

To resolve it we can just check if the connection is already added to the 
broker before adding it again :)

More proper solution would be to fix the call to processAddConnection() and 
avoid calling if the connection already established.

 


> 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
(v6.3.4#6332)

[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected

2016-01-07 Thread Ehud Kleers (JIRA) 

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

Ehud Kleers commented on AMQ-6075:
--

This might work to resolve the problem but needs to be verified - 

try {

//
CopyOnWriteArrayList connList = 
connector.getConnections();
for (TransportConnection transConn : connList) {

String connId = transConn.getConnectionId();

if (connId.equals(info.getConnectionId().toString())) {
return null;
}

}
/
broker.addConnection(context, info);
} catch (Exception e) {


> 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
(v6.3.4#6332)