Bug 114451

Summary: Need a mechanism for persistently specifying the JVM args
Product: [Retired] Red Hat Web Application Framework Reporter: Daniel BerrangĂ© <berrange>
Component: installationAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-02-05 16:04:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 113496    

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.