Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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.

share|improve this question
When running through the console, I've confirmed MaxPermSize setting is shown in the FishEye Admin SystemInfo page. – Jeremy Dec 21 '10 at 3:40

1 Answer 1

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.

# Wrapper Properties
# Working Directory

# Java Application\Program Files\Java\jdk1.6.0_25\bin\java.exe

# Java Main class.  This class must implement the WrapperListener interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1 (add lib FIRST so that log4j config gets loaded first)*.jar

# Java Library Path (location of Wrapper.DLL or

# Java Additional Parameters

# JDK 1.5 Additional Parameters for jmx"wrapper:type=Java Service Wrapper Control""C:\Atlassian\fecru-2.6.3\bin\.."

# Initial Java Heap Size (in MB)

# Maximum Java Heap Size (in MB)

# Application parameters.  Add parameters as needed starting from 1
# The first application parameter is the name of the class whose main
# method is to be called when the application is launched.  The class
# name is followed by the number of parameters to be passed to its main
# method.  Then comes the actual parameters.

# The start parameters are followed by the name of the class whose main
# method is to be called to stop the application.  The stop class name
# is followed by a flag which controls whether or not the Wrapper should
# wait for all non daemon threads to complete before exiting the JVM.
# The flag is followed by the number of parameters to be passed to the
# stop class's main method.  Finally comes the actual parameters.

# Wrapper Logging Properties
# Format of output for the console.  (See docs for formats)

# Log Level for console output.  (See docs for log levels)

# Log file to use for wrapper output logging.

# Format of output for the log file.  (See docs for formats)

# Log Level for log file output.  (See docs for log levels)

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.

# Log Level for sys/event log output.  (See docs for log levels)

# Wrapper Windows Properties
# Title to use when running as a console

# Wrapper Windows NT/2000/XP Service Properties
# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service

# Display name of the service

# Description of the service

# Service dependencies.  Add dependencies as needed starting from 1

# Mode in which the service is installed.  AUTO_START or DEMAND_START

# Allow the service to interact with the desktop.

Noteworthy Lines\Program Files\Java\jdk1.6.0_25\bin\java.exe

Full path to the JDK 'hotspot' server executable. Note, download the full JDK, not just the JRE."C:\Atlassian\fecru-2.6.3\bin.."

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.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.