The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

why after upgrade get a error when select activity source of an issue?

Woow
March 5, 2013

We recently upgraded from jira 5.0.1 to 5.2.6, but when I select a issue, and then select Activity Source, get an error:
"This list may be incomplete, as errors occurred whilst retrieving source from linked applications:

Request to http://woow-sub1:8060/ failed: Error in remote call to 'woow-sub1' (http://localhost:8060) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=TALK-10516, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Connection refused"

And log from Catalina.out:

"2013-03-06 13:35:06,121 http-bio-8080-exec-1017 ERROR sabin.ungureanu 815x510493x1 1885c7u 172.17.4.102 /browse/TALK-10516 [jirafisheyeplugin.domain.crucible.ReviewManagerImpl] (CRU Text Search) Error encountered retrieving issue reviews from 'http://woow-sub1:8060/' for 'TALK-10516'
java.io.IOException: Error in remote call to 'woow-sub1' (http://localhost:8060) [AbstractRestCommand{path='rest-service/search-v1/reviews', params={term=TALK-10516, maxReturn=50}, methodType=GET}] : Connection refused"

A have fisheye plugin installed and it's enabled.

What is the source of this error, and how can I fix-it?

Thank you!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Janet Albion
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 5, 2013

Hi Sabin,

This error indicate that JIRA can't reach the FishEye/Crucible instance that has been integrated with JIRA prior to the upgrade. If the FishEye instance is not running in the same server as JIRA 5.2.6 , you might want to re-create the application link between JIRA and FishEye or relocate the FishEye instance from JIRA side

You might want to access the URL below and check if the FishEye instance can return any result:

TAGS
AUG Leaders

Atlassian Community Events