Red Hat Bugzilla – Bug 535398
be able to customize the launcher scripts' memory settings but leave the rest of the defaults
Last modified: 2014-05-05 16:53:28 EDT
Today, if you want to increase the memory settings (-Xmx, -Xms) you need to use RHQ_SERVER_JAVA_OPTS and RHQ_AGENT_JAVA_OPTS. But this means you need to reset all the other defaults since you are completely overriding the opts.
Since memory settings are more common to want to change than the other things (like the log directory for the server), let's create a new RHQ_SERVER_MEMORY_JAVA_OPTS that lets you override those but keep the other defaults. Same for RHQ_AGENT_MEMORY_JAVA_OPTS to make it consistent for the agent as it is with the server.
We might want to consider further splitting it out and having separate env vars for heap and permgen, e.g.:
Otherwise, users could easily neglect to specify permgen setting, e.g.:
and end up with the JVM max permgen default of 64MB, which is too low for the JON Server, which needs a minimum of around 128MB.
I dont like the sound of RHQ_SERVER_*special_property*_JAVA_OPTS. We should have some sort of .env file the server sources in order to pick up its JAVA_OPTS. The people can override this easily:
a) just edit the .env directly to add/change the options
b) override the value in the .env file by specifying an environment variable. This is easy to do because the user just copies the current value of the property from the .env file, tweaks it and specifies the new value as an env. var.
Setting this to critical since its impacting customers running 1.2, e.g. case 295891
We need to NOT expose INITIAL heap. In fact I say we just have "RHQ_AGENT_HEAP_SIZE" and we automatically set the initial and max to that value. Greg and Charles can tell you why :) Customer was fine starting the server, but once it needed to process alot of agents, heap grew and the max was too much for the memory the box had. This kind of problem would have been detected much early on if initial and max were the same.
Sorry - I mean RHQ_SERVER_HEAPSIZE (not agent).
Moving features/improvements to 1.4
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2099
mass add of key word FutureFeature to help track
Charles and Mazz, what do we want to do here?
this is low priority/severity at minimum. I'm not too excited about this one - wouldn't hurt my feelings if we just closed this. I don't think its very important.