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.
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
Works with tomcat & resin.