Connectivity from Jira to Crucible fails with timeout

[Artur Shnayder]

The following error message appears in the Source tab of one of the tickets:

This list of changesets may be incomplete, as errors occurred retrieving changesets from the following repositories:

Repository Expert2 on http://crucible.ert.com:8060/ failed: Error in remote call to 'Crucible' (http://crucible.ert.com:8060) AbstractRestCommand{path='api/rest/query', params={query=select revisions from dir / where comment matches 'EXPRT-6639' order by date group by changeset return csid, rep=Expert2}, methodType=POST} : java.net.SocketTimeoutException: Read timed out

[Martin Cooper]

https://confluence.atlassian.com/display/FISHKB/FishEye+issue+or+project+tab+panel+takes+a+long+time+to+load

https://confluence.atlassian.com/display/FISHKB/ConnectTimeoutException+or+SocketTimeoutException+error+in+logs

You can increase the Timeout settings on the Fisheye Plugin - from the application Links Page in JIRA select the Fisheye Configuration Link. This will take you to the right place. Note the Fisheye Configuration link on the main admin tab does not display the timeouts settings. Going via the application links take you direct to these settings.

You can also edit the settings for what the source tab searches for and displays, lowering these settings can improve performance. Details in link above.

[Adam Myatt]

Anyone ever figure this issue out?

[JamieA]

Fisheye is slow slow slow... we always get timeouts when looking at the source tab on the project pages. You used to be able to bump up the timeout in the fisheye configuration page in jira, but I can't find that option now...

[Ilya Furmanov]

We experience same issue. It happens up to 50% of the time