The socket inactivity timeout of remote agents is 5min this means, an agent can be dead for 5 mins before Bamboo will close the transport. For this, one single bamboo agent terminated non-gracefully will within minutes lead to a disconnect of all bamboo agents due to the ActiveMQ broker blocking all queues after 5 min of the event if the dead transport is used.
This was discussed in the community also
Possible reduction of the following defaults may be useful;
- maxInactivityDuration (in bamboo.cfg.xml) from 5min to 90s
- Introduce a socket timeout on the transport of 45s
Example Broker URI configuration:
If using bamboo.cfg.xml: