After an upgrade to Jira 5.0.1 we are getting the following WARN's in the stdout.log - Could not reach provider xxxxx

[tonyboulton]

I get the following error every few minutes in the Jira-stdout.log could not reach provider FishEye, Conflence and Bamboo.

2012-03-30 10:54:18,770 StreamsCompletionService::thread-3179 WARN anonymous 653x3721x1 - 10.80.129.120 /rest/activity-stream/1.0/config atlassian.streams.internal.ActivityProviderConnectionMonitorImpl$ActivityMonitorJob Could not reach provider Fisheye; it will be omitted from the stream. The connection will be retried in 5 minutes

2012-03-30 11:06:18,787 StreamsCompletionService::thread-3195 WARN anonymous com.atlassian.streams.internal.ActivityProviderConnectionMonitorImpl:activityProviderMonitor atlassian.streams.internal.AppLinksActivityProvider Error fetching from /rest/activity-stream/1.0/config?local=true

com.atlassian.sal.api.net.ResponseConnectTimeoutException: The host did not accept the connection within timeout of 1000 ms

at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:311)

at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:158)

at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.execute(ApplicationLinkRequestAdaptor.java:85)

at com.atlassian.streams.internal.AppLinksActivityProvider.fetch(AppLinksActivityProvider.java:416)

at com.atlassian.streams.internal.AppLinksActivityProvider.getFilters(AppLinksActivityProvider.java:228)

at com.atlassian.streams.internal.ActivityProviderConnectionMonitorImpl$ActivityMonitorJob$1$1.call(ActivityProviderConnectionMonitorImpl.java:201)

at com.atlassian.streams.internal.ActivityProviderConnectionMonitorImpl$ActivityMonitorJob$1$1.call(ActivityProviderConnectionMonitorImpl.java:198)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at com.atlassian.util.concurrent.LimitedExecutor$Runner.run(LimitedExecutor.java:96)

at com.atlassian.sal.core.executor.ThreadLocalDelegateRunnable.run(ThreadLocalDelegateRunnable.java:34)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:662)

Caused by: org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 1000 ms

at org.apache.commons.httpclient.protocol.ControllerThreadSocketFactory.createSocket(ControllerThreadSocketFactory.java:96)

at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:127)

at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)

at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)

at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)

at com.atlassian.sal.core.net.HttpClientRequest.executeMethod(HttpClientRequest.java:479)

at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:306)

... 16 more

[hsuhailah]

Did you encounter any related issue despite of the warning messages? This warning message is probably misleading and might be related with this bug: https://ecosystem.atlassian.net/browse/STRM-2120

[MadhanBabu]

Hello,

I also get a similar error when connection Bamboo with Jira..

The Bamboo application is not able to connect to Jira. The logs from the Bamboo server reads:

2013-06-11 20:10:17,530 WARN [StreamsCompletionService::thread-7780] [ActivityProviderConnectionMonitorImpl$ActivityMonitorJob] Could not reach provider RB JIRA; it will be omitted from the stream. The connection will be retried in 5 minutes

Any clue why this could happen?

Also, it would be good to know if this application link is using RPC plugin under the hood to communicate?

[David Chan]

It looks like JIRA's activity stream is trying to connect another server, but it's timing out. Maybe try double checking the application links you have setup within JIRA and Fisheye or any other applications that have been integrated with JIRA.