Bug 114906 - ccm-tools should provide a default /etc/conf/envars
Summary: ccm-tools should provide a default /etc/conf/envars
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: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-04 10:36 UTC by Daniel Berrangé
Modified: 2007-04-18 17:02 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-02-19 18:33:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2004-02-04 10:36:19 UTC
Description of problem:
The ccm-tools package should install a default set of envvars suitable
for a typical production install. Probably:

JAVA_OPTS=-Xms512m -Xmx512m

since this is suitable for all JDKs. We should also probably include
some commented out examples for other configs - such as the Sun JDK
garbage collector optimizations.

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


How reproducible:


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


Expected results:


Additional info:

Comment 1 Richard Li 2004-02-04 13:42:37 UTC
what happens with the above if the machine has, say, 384MB of RAM?

Comment 2 Daniel Berrangé 2004-02-04 13:51:36 UTC
Experiance has shown us that production servers will very quickly fall
over with OutOfMemoryExceptions if you allocate < 512m, particulary,
if  they upload even moderately sized images / files. So running on a
machine with < 1 GB of RAM is not feasible. 


Comment 3 Richard Li 2004-02-04 13:54:54 UTC
Let me rephrase my question.

If I'm downloading this thing for evaluation, and I'm not running in
production, and my machine has 384MB of RAM, and I just want to click
around, will using these defaults preclude me from running at all?

Comment 4 Dennis Gregorovic 2004-02-04 17:32:14 UTC
/etc/ccm/conf/envvars is part of the ccm-tools package as of 40056.

The contents are:

  ## Environment variables to be set at ccm invocation

  ## Jave Runtime Environment parameters
  # JAVA_OPTS=-Xms512m -Xmx512m

I prefer to leave the JAVA_OPTS settings commented out for the reason
that Richard Li mentioned.  Plus, production installs should refer to
the deployment guide and use JVM settings corresponding to the
individual situation.


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