Srinath Samudrala created AMQ-8478:
--------------------------------------
Summary: Unwanted logs initiated through
triggerStartAsyncNetworkBridgeCreation
Key: AMQ-8478
URL: https://issues.apache.org/jira/browse/AMQ-8478
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.15.12
Environment: Windows + running on OpenJDK 11
discoveryURI is configured as "multicast://default"
Broker:
amq:broker id="amqBroker" brokerName="brkr-#\{jmsConfig.brokerName}"
dataDirectory="${home}/logs/jms-data"
systemExitOnShutdown="false" persistent="true" enableStatistics="true"
useJmx="true" networkConnectorStartAsync="true"
start="false">
Network Connectors:
<amq:networkConnectors >
<amq:networkConnector>
<!-- Only share global topic across the network -->
<amq:dynamicallyIncludedDestinations>
<amq:topic>
<property name="physicalName" value="#\{jmsConfig.globalTopicName}"
/>
</amq:topic>
</amq:dynamicallyIncludedDestinations>
<property name="name" value="nc-#\{jmsConfig.brokerName}" />
<property name="uri" value="#\{jmsConfig.networkConnectorUri}" />
<property name="userName" value="#\{jmsConfig.username}" />
<property name="password" value="#\{jmsConfig.password}" />
</amq:networkConnector>
</amq:networkConnectors>
Transport connectors:
<amq:transportConnectors>
<amq:transportConnector allowLinkStealing="true"
uri="tcp://0.0.0.0:#\{jmsConfig.port}">
<property name="name" value="tc-#\{jmsConfig.brokerName}" />
<property name="discoveryUri" value="#\{jmsConfig.discoveryUri}" />
</amq:transportConnector>
</amq:transportConnectors>
Reporter: Srinath Samudrala
Following logs were observed while trying to establish a network of brokers
that are embedded in an application and are part of different JVMs.
Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector:nc-134F4ECBD2E7431EAF5ED41C8F010044:BrokerService[brkr-134F4ECBD2E7431EAF5ED41C8F010044]]
[DiscoveryNetworkConnector] Establishing network connection from
vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044 to tcp://XXXXXXXX:7688
2021/12/29 09.39.37.032 WARN [triggerStartAsyncNetworkBridgeCreation:
remoteBroker=tcp://XXXXXXXX/XXXXXXXX:7688@60618, localBroker=
vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#15348] [TransportConnection] Failed
to add Connection
id=brkr-134F4ECBD2E7431EAF5ED41C8F010044->brkr-96E81CB1E0B04B569832D18D632DC202-62461-1640713916560-15350:1,
clientId=nc-134F4ECBD2E7431EAF5ED41C8F010044_brkr-96E81CB1E0B04B569832D18D632DC202_inbound_brkr-134F4ECBD2E7431EAF5ED41C8F010044
due to javax.jms.InvalidClientIDException: Broker:
brkr-134F4ECBD2E7431EAF5ED41C8F010044 - Client:
nc-134F4ECBD2E7431EAF5ED41C8F010044_brkr-96E81CB1E0B04B569832D18D632DC202_inbound_brkr-134F4ECBD2E7431EAF5ED41C8F010044
already connected from vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#4
2021/12/29 09.39.37.032 INFO [triggerStartAsyncNetworkBridgeCreation:
remoteBroker=tcp://XXXXXXXX/XXXXXXXX:7688@60618, localBroker=
vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#15348]
[DemandForwardingBridgeSupport] Network connection between
vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#15348 and
tcp://XXXXXXXX/XXXXXXXX:7688@60618 shutdown due to a local error:
javax.jms.InvalidClientIDException: Broker:
brkr-134F4ECBD2E7431EAF5ED41C8F010044 - Client:
nc-134F4ECBD2E7431EAF5ED41C8F010044_brkr-96E81CB1E0B04B569832D18D632DC202_inbound_brkr-134F4ECBD2E7431EAF5ED41C8F010044
already connected from vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#4
2021/12/29 09.39.37.040 INFO [ActiveMQ
BrokerService[brkr-134F4ECBD2E7431EAF5ED41C8F010044] Task-260]
[DemandForwardingBridgeSupport] brkr-134F4ECBD2E7431EAF5ED41C8F010044 bridge to
brkr-96E81CB1E0B04B569832D18D632DC202 stopped
2021/12/29 09.39.39.032 INFO [ActiveMQ
BrokerService[brkr-134F4ECBD2E7431EAF5ED41C8F010044] Task-262]
[TransportConnection] Stopping vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#15348
because Failed with SecurityException: Broker:
brkr-134F4ECBD2E7431EAF5ED41C8F010044 - Client:
nc-134F4ECBD2E7431EAF5ED41C8F010044_brkr-96E81CB1E0B04B569832D18D632DC202_inbound_brkr-134F4ECBD2E7431EAF5ED41C8F010044
already connected from vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#4
2021/12/29 09.39.42.469 INFO
[Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector:nc-134F4ECBD2E7431EAF5ED41C8F010044:BrokerService[brkr-134F4ECBD2E7431EAF5ED41C8F010044]]
[DiscoveryNetworkConnector] Establishing network connection from
vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044 to tcp://XXXXXXXX:7688
2021/12/29 09.39.42.481 WARN [triggerStartAsyncNetworkBridgeCreation:
remoteBroker=tcp://XXXXXXXX/XXXXXXXX:7688@60619, localBroker=
vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#15350] [TransportConnection] Failed
to add Connection
id=brkr-134F4ECBD2E7431EAF5ED41C8F010044->brkr-96E81CB1E0B04B569832D18D632DC202-62461-1640713916560-15352:1,
clientId=nc-134F4ECBD2E7431EAF5ED41C8F010044_brkr-96E81CB1E0B04B569832D18D632DC202_inbound_brkr-134F4ECBD2E7431EAF5ED41C8F010044
due to javax.jms.InvalidClientIDException: Broker:
brkr-134F4ECBD2E7431EAF5ED41C8F010044 - Client:
nc-134F4ECBD2E7431EAF5ED41C8F010044_brkr-96E81CB1E0B04B569832D18D632DC202_inbound_brkr-134F4ECBD2E7431EAF5ED41C8F010044
already connected from vm://brkr-134F4ECBD2E7431EAF5ED41C8F010044#4
For every 5 seconds, these log statements get added.
Please let me know how to fix this problem
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
