JIRA Ticket Source Tab Reports "Received status code 500"
Symptoms
When clicking the Source tab on a JIRA ticket, the following is reported:
Repository REPO_NAME on http://172.17.180.143:8060/ failed: Error in remote call to 'server_name' (http://172.17.180.143:8060) [AbstractRestCommand{path='/rest-service-fe/changeset-v1/listChangesets/', params={expand=changesets[0:20].revisions[0:29], comment=PROJ, p4JobFixed=PROJ, rep=REPO_NAME}, methodType=GET}] : Received status code 500 (Internal Server Error)At the same time the Fisheye DEBUG log messages report:
DEBUG [btpool0-220 ] fisheye.app DefaultRecentChangesetsService-listChangesets - Repository state exception
com.cenqua.fisheye.rep.RepositoryHandle$StateException: Repository is not running
at com.cenqua.fisheye.rep.RepositoryHandle.validateRepositoryRunning(RepositoryHandle.java:426)
at com.cenqua.fisheye.rep.RepositoryHandle.acquire(RepositoryHandle.java:408)
at com.cenqua.fisheye.rep.RepositoryHandle.acquireEngine(RepositoryHandle.java:377)
at com.atlassian.fisheye.spi.services.DefaultRecentChangesetsService.listChangesets(DefaultRecentChangesetsService.java:42)
at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source)Cause
JIRA is trying to retrieve data from the Fisheye repository (at the message above, named REPO_NAME), however the repository is disabled.
Resolution
In the Fisheye Administration Console click on "Repositories" and at the line of the disabled repository (REPO_NAME) click on the cog icon to view the repository operations in a dropdown menu. Click on "Enable" and then in the same menu, click "Start".
If the repo should not be enabled, then remove the project link between JIRA and Fisheye and in JIRA go to Administration > Fisheye plugin > Configure and enable "Disable for unmapped..."
Last modified on May 2, 2013
Powered by Confluence and Scroll Viewport.