sometimes jira is very slow,and as a result an error displays as below.
The JIRA server could not be contacted.This may be a temporary glitch or the server may be down.
and when i Clicks "Source" tab,jira works slowly,after few seconds,the source page will show warnings about the repository errors.
i think it may be the fisheye error.
If you find it happens periodically, you can try taking a thread dump and also enabling garbage collection logging to see if there's any performance problems on the instance. Also check to see what's happening with your server when JIRA is slow - a high CPU can often mean GC is going nuts, which can be a result of not enough heap, a bug or a naughty plugin that has decided to use up more memory than it should. These will help:
You'll need to read your logs to find out what it's pausing on, and probably increase some logging to find out what's going on here.
Start at https://confluence.atlassian.com/display/JIRAKB/JIRA+Performance+Tuning if your logs don't show anything specific
Try cleaning up the Tomcat cache to see what happens there.
If this has been fixed (I see it's an old post) feel free to comment here on what you did in case someone else encounters the same problem. ;-)
I have the same error message. I'm pretty sure it's a programming issue, since it happens to me when I create a filter that comes up with no result.
It doesn't necessarily have to be with custom fields. Also built-in fields provoke this same error. Try to filter for an assignee of which you are sure s/he doesn't have any issues assigned. You should see this same error. What's more. The filter result will show the same counter statistics (1/10) as the last filter you ran before getting this error.
Regretfully I have not yet found a solution. Anyone has?
This can happen when a query passes validation but throws an error, for instance when a function runs. The error message is incorrect, it should say something like "the query had an error", not "the server could not be contacted". I don't think this is the issue the OP has, sounds like slow fisheye. Is there any other kind of fisheye?
I had this same issue, mine was because of Workflow... When issues is moved to DONE in a workflow, I use to get this error... it was because I was using a screen to show up when the issue is moved to DONE... A value was set in Post Function to show up a screen... when removed, it worked...
I have to see why that screen was causing this issue, atleast now I can push my issues to DONE...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot