Bug 114451 - Need a mechanism for persistently specifying the JVM args
Summary: Need a mechanism for persistently specifying the JVM args
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dennis Gregorovic
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks: 113496
TreeView+ depends on / blocked
 
Reported: 2004-01-28 11:46 UTC by Daniel Berrangé
Modified: 2007-04-18 17:02 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-02-05 16:04:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2004-01-28 11:46:32 UTC
Description of problem:
On a production server we need to set JVM args to increase memory size
to 1.5 GB, and change garbage collector flags, etc. This can be done
on the command line when running 'ccm start', but its not acceptable
to expect the administrator to remember these args every time they
start the 'ccm' command. These settings should be persisted in some
config file.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

This ties in with bug 114449, since the init script should pick up the
JVM args config.

Comment 1 Dennis Gregorovic 2004-01-28 18:56:22 UTC
as of @39840, the user can set per-ccm-instance variables with
$CCM_HOME/conf/envvars.  So, to set some JVM args for the default ccm
install on a machine, add the following line to
/usr/share/ccm/conf/envvars:

JAVA_OPTS=-Xms256m -Xmx256m

Comment 2 Jon Orris 2004-02-05 16:04:40 UTC
Works with tomcat & resin.


Note You need to log in before you can comment on or make changes to this bug.