Agent disconnected: "java.net.ConnectException: Connection timed out"
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The remote agent is dropping out due to errors similar to:
1
java.net.ConnectException: Connection timed out
Resolution
Firewall/Router: Ensure that you don't have a firewall/router which might be closing network connections due to inactivity.
Low Network Throughput: The error can also occur, whilst sending large messages over slow network link:
This problem arises because the ActiveMQ message broker continuously checks for activity on a socket, and whilst building a large message in the TCP socket buffer, the inactivity monitor will time out
As the document suggests, edit your <Bamboo_Home>/bamboo.cfg.xml file and update the section below. Set the maxInactivityDuration value to a number > 300000:
1
<property name="bamboo.jms.broker.client.uri">failover:(tcp://192.168.35.128:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&initialReconnectDelay=15000</property>Was this helpful?