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 vote
Nick Pellow Atlassian Team Nov 10, 2013

The fix for https://confluence.atlassian.com/display/FISHKB/Web+interface+does+not+load+after+upgrade+from+2.10.x+to+3.0 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 support.atlassian.com 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.

Cheers,

Nick

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:

https://confluence.atlassian.com/display/FISHKB/Web+interface+does+not+load+after+upgrade+from+2.10.x+to+3.0

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.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Trello

Alice Camilla on organizing your work/life/fandoms with Trello!

@Alice Camilla is a university student, currently writing her MA thesis in Archaeology. She's also a freelance blogger and content creator, writing about geeky stuff from productivity apps to JR...

39 views 1 6
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you