I have been trying to setup Atlassian Fisheye/Crucible as a service on Win 2K3 R2 for two weeks. I keep getting various "java.lang.OutOfMemoryError: PermGen space" errors, which crash Fisheye and force me to restart the service.
I've followed the example on the Atlassian support site to configure MaxPermSize within the service wrapper. However, when I check SysInfo inside the Fisheye Admin pages and the debug log, I don't see any confirmation. The Java Heap info is in both places, so I'd expect the MaxPermSize setting to show up in both places.
The error is persisting and Atlassian support has been little help.
I appreciate any help.
You can set this in your Wrapper.conf file. Here's my config file and this is working great for me, I'm using this with Fisheye 2.6.3 running on Windows Server 2008 R2. This file is mostly identical to the sample/default configuration, with a few important additions that I'll comment on at the end.
Noteworthy Lines
Full path to the JDK 'hotspot' server executable. Note, download the full JDK, not just the JRE.
None of the above are shown in the Atlassian documentation, I have added these over time through trial and error. When FeCru is first started under the service wrapper, it may stop with an out of memory error, the 'MaxPermSize' line fixes that.
I've also found it is necessary to specify FISHEYE_INST as shown above. I have no idea why the path is specified with
/..
on the end, it was like that in the example I found. Some cooky linux ritual, no doubt. The other lines, I can't remember what they were for, but I added them for some reason or another and didn't document why. Nobody's perfect ;-)Heap memory allocations increased from the defaults - I index some fairly meaty repositories and I could afford the extra resources - you may get away with the default smaller allocations.