Long running search times out

[sinhote]

Hi,

First of all, let me congratulate you on your effort to bring the Atlassian Mylyn connector back! It's something I've been longing for a long time!

I've downloaded it and configured my company's JIRA server, but I constantly get a timeout error when I try to download the task list. FYI, I'm currently working from home and using a VPN, so I need to define a proxy in Eclipse, but I could configure and test the server connection without issues, and I could correctly pull a custom issue filter from the server, too (so it seems the connection works).

The error reads:

20,000 milliseconds timeout on connection http-outgoing-2 [ACTIVE]

Let me know if you need any more details.

[sinhote]

Hi,

It turns out that it works with a filter returning fewer results, so I guess this is a question of increasing the timeout or making it configurable.

[gnl42]

Hi, that's "good" news at least, easier to change. If you run the same, or similar query through the Web UI how long does it take?

There should be a stack trace with the error if you open it. Can you add it

[gnl42]

Hi, I was able to trigger the error myself using my company server. I'll see what I can do

me.glindholm.connector.eclipse.internal.jira.core.service.JiraException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.net.SocketTimeoutException: 20,000 milliseconds timeout on connection http-outgoing-5 [ACTIVE] at me.glindholm.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.call(JiraRestClientAdapter.java:876) at me.glindholm.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.getIssues(JiraRestClientAdapter.java:374) at me.glindholm.connector.eclipse.internal.jira.core.service.JiraClient.findIssues(JiraClient.java:358) at me.glindholm.connector.eclipse.internal.jira.core.service.JiraClient.findIssues(JiraClient.java:351) at me.glindholm.connector.eclipse.internal.jira.core.service.JiraClient.search(JiraClient.java:731) at me.glindholm.connector.eclipse.internal.jira.core.JiraRepositoryConnector.performQuery(JiraRepositoryConnector.java:139) at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.synchronizeQuery(SynchronizeQueriesJob.java:306) at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.synchronizeQueries(SynchronizeQueriesJob.java:263) at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.run(SynchronizeQueriesJob.java:194) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.net.SocketTimeoutException: 20,000 milliseconds timeout on connection http-outgoing-5 [ACTIVE] at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396) at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073) at io.atlassian.util.concurrent.Promises$OfStage.get(Promises.java:353) at me.glindholm.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:101) at me.glindholm.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter$4.call(JiraRestClientAdapter.java:379) at me.glindholm.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter$4.call(JiraRestClientAdapter.java:1) at me.glindholm.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.call(JiraRestClientAdapter.java:831) ... 9 more Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: 20,000 milliseconds timeout on connection http-outgoing-5 [ACTIVE] at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.lambda$doExecute$5(ApacheAsyncHttpClient.java:328) at io.atlassian.util.concurrent.Promises.lambda$biFunction$7(Promises.java:424) at java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934) at java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911) at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$1.lambda$doFailed$1(SettableFuturePromiseHttpPromiseAsyncClient.java:42) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.runInContext(SettableFuturePromiseHttpPromiseAsyncClient.java:61) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.run(SettableFuturePromiseHttpPromiseAsyncClient.java:129) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.net.SocketTimeoutException: 20,000 milliseconds timeout on connection http-outgoing-5 [ACTIVE] at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.timeout(HttpAsyncRequestExecutor.java:387) at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:98) at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:40) at org.apache.http.impl.nio.reactor.AbstractIODispatch.timeout(AbstractIODispatch.java:175) at org.apache.http.impl.nio.reactor.BaseIOReactor.sessionTimedOut(BaseIOReactor.java:261) at org.apache.http.impl.nio.reactor.AbstractIOReactor.timeoutCheck(AbstractIOReactor.java:506) at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:211) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591) ... 1 more

[gnl42]

HI, I've fixed the timeout issue. It is now 10 minutes (some forgotten code in the migration).

If you are expecting a ton of issues you may want to take a look at the 'Search Results' on the Repository Settings popup:

[sinhote]

Hey,

Sorry for not responding to this. Thanks for fixing it so quickly! I got the latest version and it works like a charm. Keep up the good work! Thanks a million!