JIRA fails to retrieve Fisheye data - Failed to parse Fisheye response
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
Symptoms
The following appears in JIRA when trying to view the "All" Tab (Activities > All):
1
2
3
4
5
6
7
8
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
Request to http://test.atlassian.com/fisheye/ failed: Error in remote call to 'Fisheye / Crucible' (http://test.atlassian.com/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params=
{query=test-9, expand=changesets[-1:-1].revisions[0:2],reviews}
,
methodType=GET}] : Failed to parse FishEye response: Error on line 6 of
document : The element type "meta" must be terminated by the matching
end-tag "</meta>". Nested exception: The element type "meta" must
be terminated by the matching end-tag "</meta>".The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
2013-02-12 17:05:06,821 http-8041-5 ERROR user 1025x3761x2 1izbhoo 55.55.12.12,10.16.16.20 /rest/tabs/1.0/com.atlassian.jirafisheyeplugin:crucible-issuepanel/test-9 [jirafisheyeplugin.domain.crucible.ReviewManagerImpl] (CRU Text Search) Error encountered retrieving issue reviews from 'http://test.atlassian.com/fisheye/' for 'test-9'
java.io.IOException: Error in remote call to 'Fisheye / Crucible' (http://test.atlassian.com/fisheye) [AbstractRestCommand{path='rest-service/search-v1/reviews', params={term=test-9, maxReturn=50}, methodType=GET}] : Failed to parse FishEye response: Error on line 6 of document : The element type "meta" must be terminated by the matching end-tag "</meta>". Nested exception: The element type "meta" must be terminated by the matching end-tag "</meta>".
...
... 167 more
Caused by: org.dom4j.DocumentException: Error on line 6 of document : The element type "meta" must be terminated by the matching end-tag "</meta>". Nested exception: The element type "meta" must be terminated by the matching end-tag "</meta>".
...
... 175 more
Cause
JIRA's outbound communication is getting routed through the intranet proxy to contact Fisheye.
Resolution
Proxy support is configured by passing certain arguments to the Java Virtual Machine on application start. See this KB article for configuring JIRA:
Was this helpful?