we get the following indexing error message

Gerhard Bartha March 9, 2018

2018/03/09 11:53:40 External service error
com.xiplink.jira.git.exception.external.WrappedGitlabAPIException: External service error
at com.xiplink.jira.git.integration.gitlab.CachedGitLabApi.getRepositories(CachedGitLabApi.java:86)
at com.xiplink.jira.git.integration.gitlab.GitLabApiService.scan(GitLabApiService.java:140)
at com.xiplink.jira.git.gitmanager.ExternalServiceGitManager.activate(ExternalServiceGitManager.java:46)
at com.xiplink.jira.git.async.BigReindexTask.filterValid(BigReindexTask.java:131)
at com.xiplink.jira.git.async.BigReindexTask.run(BigReindexTask.java:84)
at com.xiplink.jira.git.async.AsyncProcessorImpl$AsyncTaskWrapper.run(AsyncProcessorImpl.java:105)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.Error: java.net.SocketTimeoutException: Read timed out
at org.gitlab.api.http.GitlabHTTPRequestor$1.fetch(GitlabHTTPRequestor.java:277)
at org.gitlab.api.http.GitlabHTTPRequestor$1.hasNext(GitlabHTTPRequestor.java:231)
at org.gitlab.api.http.GitlabHTTPRequestor.getAll(GitlabHTTPRequestor.java:199)
at org.gitlab.api.GitlabAPI.getProjects(GitlabAPI.java:836)
at com.bigbrassband.common.integration.GitLabApiPool$GitLabApiWrapper$1.call(GitLabApiPool.java:239)
at com.bigbrassband.common.integration.GitLabApiPool$GitLabApiWrapper$1.call(GitLabApiPool.java:1)
at com.bigbrassband.common.integration.GitLabApiPool$GitLabApiWrapper.doSafely(GitLabApiPool.java:210)
at com.bigbrassband.common.integration.GitLabApiPool$GitLabApiWrapper.getProjects(GitLabApiPool.java:236)
at com.xiplink.jira.git.integration.gitlab.CachedGitLabApi.getRepositories(CachedGitLabApi.java:77)
... 10 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
at sun.security.ssl.InputRecord.read(InputRecord.java:503)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1536)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at org.gitlab.api.http.GitlabHTTPRequestor.parse(GitlabHTTPRequestor.java:416)
at org.gitlab.api.http.GitlabHTTPRequestor.access$2(GitlabHTTPRequestor.java:410)
at org.gitlab.api.http.GitlabHTTPRequestor$1.fetch(GitlabHTTPRequestor.java:270)
... 18 more

 

what is the problem and how can we fix it?

1 answer

1 accepted

0 votes
Answer accepted
Mark L. Smith
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 9, 2018

Hi Gerhard,

 

You're getting a timeout on trying to get on the projects API at GitLab.

There's some known GitLab issues with this --- it generally affects only gitlab.com and only some users.

Are you trying to connect to gitlab.com?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events