Summary

As part of a remote agent startup process,  Bamboo Server Broker URL is tested for validity.

INFO   | jvm 1    | 2023/07/04 16:10:10 | 2023-07-04 16:10:10,343 INFO [AgentRunnerThread] [BambooActiveMQConnectionFactory] Broker URI: ssl://ip-192-168-1-89.us-west-2.compute.internal:54663?socket.verifyHostName=false&wireFormat.maxInactivityDuration=300000 is valid.

When the test is complete, the agent closes the connection which causes ActiveMq to raise an exception, which logs a warning message in the Bamboo server log.

[ActiveMQ BrokerService[bamboo] Task-130] [TransportConnector$1] Could not accept connection from tcp://1.1.1.0:39452: Connection or outbound has closed (Connection or outbound has closed). 

Note: The exception is a harmless one that can be safely ignored.

Suggestion

Find a method to test the Broker URL without raising an exception.

Workaround

Add custom Log4J entries on the Bamboo server by changing the default WARN log level to ERROR on the following classes:

• org.apache.activemq.broker.TransportConnector
• org.apache.activemq.broker.TransportConnection

It is recommended to add the entries to the <bamboo-Install>/atlassian-bamboo/WEB-INF/classes/log4j2.properties file so the custom configuration can survive an application restart. E.g.:

logger.activemq-added-TransportConnector.level = ERROR
logger.activemq-added-TransportConnector.name = org.apache.activemq.broker.TransportConnector
logger.activemq-added-TransportConnection.level = ERROR
logger.activemq-added-TransportConnection.name = org.apache.activemq.broker.TransportConnection