Details
-
Suggestion
-
Resolution: Fixed
Description
Currently the standalone setenv.sh has a structure like this
JAVA_OPTS="-Xms128m -Xmx256m $JAVA_OPTS -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true " # use this if you want to import data without notifications #JAVA_OPTS=" -Datlassian.mail.senddisabled=true -Datlassian.mail.fetchdisabled=true -Datlassian.mail.popdisabled=true $JAVA_OPTS " export JAVA_OPTS echo "If you encounter issues starting up JIRA Standalone Edition, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide"
Customers some times get it wrong when we ask them to insert certain options like GC settings and so on
Perhaps we should tweak this file to include the most common settings (commented out of course) so support can ask them to simply "uncomment" option X. For example may something like this
# # Change this to change the amount of mmemory that JIRA uses blah blah see hear for more info http://jira.atlasiian/memory_stuff MEMORY_MIN="-Xms128m" MEMORY_MAX="-Xmx256m" # # Un comment this option to have the JVM produce a memory should JIRA run out of memory. This will help support work stuff out # #MEMORY_DUMP_OOM="-XX:+HeapDumpOnOutOfMemoryError" # # # # GC_LOGGING="-verbose:gc" # GC_LOGGIN_FILE="Xloggc:gc.log" .. .. and so on on and so on .. JAVA_OPTS="$MEMORY_MIN $MEMORY_MAX $MEMORY_DUMP_OOM $GC_LOGGING $GC_LOGGIN_FILE -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true"
This would help support by giving them more precise ways of describing what options they want set on (eg they can say to the customer uncomment MEMORY_DUMP_ON_OOM please?) and also
to more clearly explain all the options to customer since not every one is a Java command line whiz!
This would reduce the noise to information ratio for JIRA admins.