Agent remains in loading: " Address already in use"

Still need help?

The Atlassian Community is here for you.

Ask the community


Agents are not connecting and but the server is able to see them loading.

From Cog icon >> Overview >> Agents >> Online remote agents (tab) the following message can be seen: 

Nov 12, 2017 2:55:32 PM A remote agent is loading on (


One of the possible causes could be the address already in use. If this is the case the following can be found in the server logs:

2017-11-12 14:48:44,686 ERROR [localhost-startStop-1] [BambooBrokerService] Unable to start JMS connector at nio:// Failed to bind to server socket: nio:// due to: Address already in use
  at org.apache.activemq.util.IOExceptionSupport.create(
  at org.apache.activemq.transport.tcp.TcpTransportServer.bind(
  at org.apache.activemq.transport.tcp.TcpTransportFactory.doBind(
  at org.apache.activemq.transport.TransportFactorySupport.bind(
  at com.atlassian.bamboo.amq.BambooBrokerService.startConnector(
  at com.atlassian.bamboo.amq.BambooBrokerService.addStartedConnectors(
  at com.atlassian.bamboo.buildqueue.manager.RemoteAgentManagerImpl.startOrStopConnectors(
  at com.atlassian.bamboo.buildqueue.manager.RemoteAgentManagerImpl.start(
  at com.atlassian.bamboo.container.BambooContainer.start(
  at com.atlassian.bamboo.upgrade.UpgradeLauncher.upgradeAndStartBamboo(
  at com.atlassian.bamboo.upgrade.UpgradeLauncher.contextInitialized(
  at org.apache.catalina.core.StandardContext.listenerStart(
  at org.apache.catalina.core.StandardContext.startInternal(
  at org.apache.catalina.util.LifecycleBase.start(
  at org.apache.catalina.core.ContainerBase$
  at org.apache.catalina.core.ContainerBase$
  at java.util.concurrent.ThreadPoolExecutor.runWorker(
  at java.util.concurrent.ThreadPoolExecutor$
Caused by: Address already in use
  at Method)
  at org.apache.activemq.transport.nio.NIOTransportFactory$2.createServerSocket(
  at org.apache.activemq.transport.tcp.TcpTransportServer.bind(
  ... 20 more


This mostly happens when two instances of Bamboo are running on the same server. It could be the case of having both production and development instances with broker configured to listen on 54663.

In cases where there is only one Bamboo instance and binding error still remains, the netstat command can be helpful.
The following can be used to diagnose what process is holding the port:

Windowsnetstat-an | findstr54663
Unix likenetstat -an | grep 54663


  1. Shutdown the instance with the error Address already in use

  2. Edit the <Bamboo_Home>/bamboo.cfg.xml file and update the port in the following two lines:

    <property name="">failover:(tcp://bamboo_server_host:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&amp;initialReconnectDelay=15000</property>
    <property name="">tcp://</property>
    tip/resting Created with Sketch.

    This change can be performed also from the Bamboo UI (Cog icon >> Overview >> General configuration) in versions above 5.x.

  3. Restart your Bamboo server for the changes to take effect.

Last modified on Nov 12, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.