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

Why can't fisheye 3.8.1 start ?



We use to have FishEye in version 2.7.3 but we tried to install the new Fisheye 3.8 (We also tried FishEye 3.8.1), it worked great with Java6 but now that we upgrade to java7 we can't start it anymore .. Even stranger, the fecru-2.7.3 still works well with this JDK, only fecru-3.8+ won't start anymore


Server log :

2015-07-01 10:59:03,881 INFO - See - Boiler Bay Inc
2015-07-01 10:59:03,881 INFO - InfinityDB is Copyight (C) 2001-2013 Roger L. Deran, all rights reserved.
2015-07-01 10:59:03,881 INFO - InfinityDB has been Licensed to Atlassian
2015-07-01 10:59:03,882 INFO - for distribution in FishEye and Crucible.
2015-07-01 10:59:03,882 INFO - Atlassian Pty Ltd (ABN 53 102 443 916)
2015-07-01 10:59:03,882 INFO - of 341 George St., Sydney, New South Wales, 2000 Australia
2015-07-01 10:59:04,153 INFO - UpgradeManager started.
2015-07-01 10:59:04,221 INFO - loading config from file: /fisheye/fecru-3.8.1/config.xml
2015-07-01 10:59:04,758 INFO - FishEye: Commercial License registered to xxxxx.
2015-07-01 10:59:05,113 INFO - Adding secondary content dir of /fisheye/fecru-3.8.1/content
2015-07-01 10:59:13,912 INFO - Starting database...
2015-07-01 10:59:14,807 INFO - BoneCP - tracking statements enabled for pool [mainPool]
2015-07-01 10:59:16,572 INFO - BoneCP - tracking statements enabled for pool [retriablePool]
2015-07-01 10:59:17,410 INFO - Database started.
2015-07-01 10:59:19,225 INFO - Starting plugin system...
2015-07-01 10:59:25,664 INFO - Mail system not configured.

... then nothing happens sad

Our java version is 

java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr6-20131015_01(SR6))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20131013_170512 (JIT enabled, AOT enabled)


Sometimes after 15 or 20 minutes (where we can't access at all the server), we can see this :

Exception in thread "Finalizer thread" java.lang.OutOfMemoryError: Java heap space
at Method)
at java.lang.J9VMInternals.runFinalize(
Exception in thread "PAGE_WRITER:16384" java.lang.OutOfMemoryError: Java heap space
at com.persistit.Persistit.getThreadLocalIntArray(
at com.persistit.Buffer.getRepackPlanBuffer(
at com.persistit.Buffer.repack(
at com.persistit.Buffer.clearSlack(
at com.persistit.Buffer.writePage(
at com.persistit.Buffer.writePage(
at com.persistit.BufferPool.writeDirtyBuffers(
at com.persistit.BufferPool$PageWriter.runTask(


The config.xml is good as it use to works when the server was running with java 1.6; Do you guys have any ideas on how to debug this issue (no real logs/error or anything..) or fix this ?

4 answers

1 accepted

0 votes
Answer accepted

As told in a comment, the JDK was the issue : Instead of using IBM 1.7 we are now using Oracle 1.7 and everything works smoothly.

Hi Daniel,


Oh yeah i forgot, i'll try to log a ticket with the support smile

About java8, I though about that, but our infrastructure policy doesn't want to upgrade the server to java8 sad

(Added information -> Fisheye 3.7.1 is working fine ..)

You might want to upgrade to java8 and check with that. Another item that I've run into one cloud based servers is that they run out of entropy ( see ) and the start up of tomcat would just hang. I don't know if this is the case with Fisheye but I know with JIRA, Confluence etc it's the case... 

Otherwise you might want to file a support ticket with

> java.lang.OutOfMemoryError: Java heap space Version 3 is a lot more memory hungry than v2 and used to have huge memory leaks as well...

Yup but version 3.7.1 works like a charm on the same server :( Only versions 3.8 and 3.8.1 can't boot and throw outOfMemory 10/20minutes after startup (well, I won't call it startup as we can't access the application, the jetty server is not even started)

Add more heap to allow it to start and then open a support case, then.

Ok the support team helped manage to find that our JDK was the issue .. we were using IBM 1.7 instead of Oracle 1.7 .. Everything works like a charm now :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

#JiraHeroes May '22 Spotlight: Daniel Cave

At Atlassian, we take great pride in the software we ship, and even greater pride in the success our customers achieve when they use our products. #JiraHeroes is our new monthly spotlight series&nbsp...

856 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you