When to expect Bamboo to move to polling from event driven build detection
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Summary
When there is a network connection error between Bitbucket and Bamboo, Bamboo will attempt to contact Bitbucket by changing from event-driven builds to polling. This comes in handy when Bitbucket is not able to make a connection to Bamboo but Bamboo is able to make a connection to Bitbucket. This can happen during any network slowdown or interruption.
Environment
Bamboo
Diagnosis
When a network interruption happens, here is an example log:
2021-02-19 14:20:37,071 INFO scheduler_Worker-1 RemoteConnectionTester Exception requesting status for remote host Bitbucket (f2be204e-78ab-367d-a6b9-70dfcf6447d2) https://internal.bitbucket.atlassian.com stash2021-02-19 14:20:37,071 INFO scheduler_Worker-1 RemoteConnectionTester Exception requesting status for remote host Bitbucket (f2be204e-78ab-367d-a6b9-70dfcf6447d2) https://internal.bitbucket.atlassian.com com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:106)Cause
There are several causes of this issue. All of them are linked to excessive resource usage:
- A network problem between Bitbucket and Bamboo
- Bitbucket is having a problem responding
- The network is overloaded with requests
Solution
Reduce network saturation and congestion. Fix network issue.