Jira startup stuck at indexing due to connection timeout to Bitbucket cloud endpoint
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
Summary
Jira startup can take long time when Jira is configured with Bitbucket cloud integration if the cloud endpoints are not reachable by the node.
Environment
9.4.11
Diagnosis
In case of this problem, following error can be seen in the logs.
1
2
3
4
5
6
7
8
9
10
IssueIndexer:thread ERROR [c.a.j.p.d.spi.bitbucket.BitbucketCommunicator] Exception while trying to fetch UUID from OAUTH credentials. Check if the credentials are correct.
com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BitbucketRequestException: Failed to execute request: https://api.bitbucket.org/2.0
...
Caused by: java.net.SocketException: Connection timed out (Read failed)
at java.base/java.net.SocketInputStream.socketRead0(Native Method)
at java.base/java.net.SocketInputStream.socketRead(SocketInputStream.java:115)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
at java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:484)
...In the thread dump files, it is also possible to see that indexer thread is waiting for the endpoint.
Cause
This issue can occur if Jira is integrated with Bitbucket cloud but is unable to access the cloud endpoints.
Solution
The IP addresses in the following article should be configured to be accessible by Jira instance:
Was this helpful?