Why can't fisheye 3.8.1 start ?

[Florian RUYNAT]

Hi,

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 infinitydb.com - 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 

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 java.util.zip.ZipFile.close(Native Method)
at java.util.zip.ZipFile.close(ZipFile.java:660)
at java.util.zip.ZipFile.finalize(ZipFile.java:680)
at java.lang.J9VMInternals.runFinalize(J9VMInternals.java:489)
Exception in thread "PAGE_WRITER:16384" java.lang.OutOfMemoryError: Java heap space
at com.persistit.Persistit.getThreadLocalIntArray(Persistit.java:2486)
at com.persistit.Buffer.getRepackPlanBuffer(Buffer.java:3433)
at com.persistit.Buffer.repack(Buffer.java:3087)
at com.persistit.Buffer.clearSlack(Buffer.java:613)
at com.persistit.Buffer.writePage(Buffer.java:528)
at com.persistit.Buffer.writePage(Buffer.java:517)
at com.persistit.BufferPool.writeDirtyBuffers(BufferPool.java:1122)
at com.persistit.BufferPool$PageWriter.runTask(BufferPool.java:1375)
at com.persistit.IOTaskRunnable.run(IOTaskRunnable.java:143)
at java.lang.Thread.run(Thread.java:804)

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 ?

[Florian RUYNAT · Accepted solution]

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.

[Florian RUYNAT]

Hi Daniel,

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

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

[Florian RUYNAT]

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

[Daniel Wester]

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 https://major.io/2007/07/01/check-available-entropy-in-linux/ ) 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 https://support.atlassian.com

[Sergey Svishchev]

> 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...

[Florian RUYNAT]

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)

[Sergey Svishchev]

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

[Florian RUYNAT]

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 :)