Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Fisheye/Crucible startup has become very slow

We've been using F/C for years and it typically takes 2-3 minutes to start up. At some point in recent months, the startup became noticeably slower. For instance, when the log says "Starting plugin system...", it now takes about 10 minutes before moving on to the next step. Now we seem to have an additional long delay after getting the message telling us that we are not running the latest version (3.1.5 is the latest as I write this; we are currently running 3.0.1). The log has been sitting on this message for over 30 minutes, I'm not confident that it will ever complete the startup process.

I have verified that there is lots of disk space and memory available, and the CPU on the machine is mostly idle.

Any idea why startup times would have degraded, and what we can do to improve/fix it?

3 answers

1 accepted

0 votes
Answer accepted
Nick Atlassian Team Nov 10, 2013

The fix for should definitely be in 3.1 and you shouldn't see the old plugin OSGi Caches getting in the way of the new plugin versions anymore.

When you see a slow FishEye/Crucible startup, please ensure you are starting with the --debug flag and take some thread dumps:

kill -3 <PID>

and create a support ticket at to have the thread dumps and DEBUG logs investigated. Seeing what the threads are doing will make it easier for us to diagnose the exact cause of the issue.



When I first followed the procedure in the link from my first comment, I only renamed the osgi-cache directory since our FISHEYE_INST directory is external to the F/C install directory. I didn't think a complete reinstall was necessary in that case. When that didn't work, I went ahead with a complete reinstall (which took hours due to the amount of data to be copied over). Now F/C is working again, and it starts up much more quickly than we had become used to.

Another user comment says that this fix only works temporarily, but we'll keep our fingers crossed.

It seems that we are now running into the following issue, which explains a lot of our slow startup (it takes a long time to timeout initializing the wrong plugin versions), although the suggested course of action doesn't seem to fix it:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events