Summary

If a build tries to communicate to an endpoint and this doesn't resolve, and if the type of request doesn't time out, then the build will get stuck and it can't be stopped manually.

Environment

• Observed in Bamboo 7.1.2.
• Running a build that needs to contact or download something from an endpoint that is not reachable.

Diagnosis

For this diagnosis, we used a "Deployment Tomcat application" task. While running the build, this is observed in the build log:

simple  23-Jul-2021 12:25:25    Trying to retrieve Tomcat details from http://myserver.com/manager/text/serverinfo
(... long time passed until a stop is requested ...)
error   23-Jul-2021 12:46:15    Force Stop build feature is enabled for current plan. Either Bamboo has detected the build has hung or it has been manually stopped.

The first line shows the process trying to contact http://myserver.com/manager/text/serverinfo. This step never times out and the build keeps trying to connect to the server. Since the subcommand (trying to contact myserver.com) is still alive, Bamboo can't stop the build, therefore the build is hung.

Cause

The problem in this scenario relies either on the network or the network configuration in one of the endpoints. A quick way to prove that it's a connectivity issue is by trying to contact the endpoint from command line, from the same machine running the build. In this example, this test will suffice:

$ wget http://myserver.com/manager/text/serverinfo
HTTP request sent, awaiting response...

This example above did not receive any response, therefore it confirms the problem. A response needs to be present, whether it's successful or not:

$ wget http://myserver.com/manager/text/serverinfo
HTTP request sent, awaiting response...200

$ wget http://myserver.com/manager/text/serverinfo
HTTP request sent, awaiting response...404

Solution

Please contact your network administrator, since the problem exists outside of Bamboo