Troubleshooting Remote Agents

Related content

Still need help?

Technical Overview of Remote Agent Connectivity Mechanism

The communication between the remote agent and server is bi-directional. The connection is initiated by the remote agent.The communication between the remote agent and server is done through two protocols, HTTP and JMS on top of unicast TCP connections.

The HTTP protocol is used for the initial registration to the server and bootstrapping on the HTTP(s) connector of the server.Artifacts are also transferred using this protocol over the main connector of the server.The JMS protocol is used for other communications (such as job dispatching, heartbeat messages) together with the Apache ActiveMQ (AMQ) message broker.

HTTP Connection

The agent will usually connect to the server using the same Bamboo URL used for general user access. The URL is set during the agent installation and can be changed later as described here.

JMS Connection

This connection will be established to the address configured in Bamboo broker at <Bamboo_Home>/bamboo.cfg.xml file.

The address should NOT be set to localhost. Ideally, the agent should reach the server directly to it's IP or hostname. If a reverse proxyaddress is set here, please make sure the proxy is correctly configured to redirect the broker TCP traffic.

Bamboo with a reverse proxy

If Bamboo is running behind a reverse proxy and the remote agent is getting trouble to connect with Bamboo (in the first stages of connection - using HTTP protocol) or experiencing artifact transfer problems, it might be worth to bypass the proxy to check if it could be causing the issue. The following document can be used for this purpose: