You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2006/06/08 19:55:51 UTC
[jira] Commented: (AMQ-738) Broker does not recognize failed broker
upon reconnect
[ https://issues.apache.org/activemq/browse/AMQ-738?page=comments#action_36265 ]
james strachan commented on AMQ-738:
------------------------------------
Just out of interest - how had you created this network?
> Broker does not recognize failed broker upon reconnect
> ------------------------------------------------------
>
> Key: AMQ-738
> URL: https://issues.apache.org/activemq/browse/AMQ-738
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Reporter: Christopher G. Stach II
>
>
> After normal shutdown of a broker and bring it back up, the first broker reports this error:
> [11:07:15.162] Establishing network connection between from vm://app1-test?network=true to tcp://10.xxx:49995
> [11:07:15.165] Starting a network connection between vm://app1-test#20 and tcp://null:0 has been established.
> [11:07:15.294] Async error occurred: javax.jms.InvalidClientIDException: Broker: app1-test - Client: NC_app2-test_inboundapp1-test already connected
> [11:07:15.294] javax.jms.InvalidClientIDException: Broker: app1-test - Client: NC_app2-test_inboundapp1-test already connected
> [11:07:15.294] at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
> [11:07:15.294] at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
> [11:07:15.294] at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
> [11:07:15.294] at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
> [11:07:15.294] at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
> [11:07:15.294] at org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
> [11:07:15.294] at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
> [11:07:15.294] at org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> [11:07:15.294] at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> [11:07:15.294] at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> [11:07:15.294] at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> [11:07:15.294] at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> [11:07:15.294] at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> [11:07:15.294] at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> [11:07:15.294] at org.apache.activemq.network.DemandForwardingBridgeSupport.startLocalBridge(DemandForwardingBridgeSupport.java:192)
> [11:07:15.294] at org.apache.activemq.network.DemandForwardingBridgeSupport$3.run(DemandForwardingBridgeSupport.java:162)
> [11:07:15.327] Network connection between vm://app1-test#20 and tcp://app2.xxx/10.xxx:49995(app2-test) has been established.
> [11:07:15.347] Unexpected local command: ConnectionError {commandId = 2, responseRequired = false, connectionId = null, exception = javax.jms.InvalidClientIDException: Broker: app1-test - Client: NC_app2-test_inboundapp1-test already connected}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira