New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-14540
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Brad Baker [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

setenv.sh in standalone should be tweaked to have more pre-configured options

Created: 27/Feb/08 06:22 PM   Updated: 27/Feb/08 06:24 PM
Component/s: Installation
Affects Version/s: 3.12.2
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Brad Baker [Atlassian]
Since last comment: 26 weeks ago
Labels: support_improvement


 Description  « Hide
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.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.