An incorrect environment variable in the 'Tuning the Server JVM' section of the Configuring JBoss ON Servers, Agents, and Storage Nodes guide caused issues with changing the heapsize on the JBoss ON server. The incorrect parameter RHQ_CONTROL_JAVA_OPTS is now corrected with RHQ_SERVER_JAVA_OPTS, which now allows the heapsize to be changed as expected.
[Admin_Config] Ready for review.
Description of problem:
Per the documentation for Tuning the Server JVM - https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.2/html/Admin_and_Config/server-jvm.html
It says to edit the rhqctl and set the RHQ_CONTROL_JAVA_OPTS="-Xms512M -Xmx1024M -XX:MaxPermSize=128M -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true"
This does not affect the server's Heap, it still uses the default set in the /bin/internal/rhq-server.sh script.
I don't know if this is a doc bug directing you to the wrong file, or a product bug where changing the settings in rhqctl SHOULD change the server heap size
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Stop the server. Edit the rhqctl and change the heapsize in RHQ_CONTROL_JAVA_OPTS="-Xms512M -Xmx2048M -XX:MaxPermSize=128M -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true"
2. Restart the server.
3. Run ps -fe and look at the process /home/dsteigne/NotBackedUp/jdk1.7.0_51/bin/java -D[Standalone] -XX:+UseCompressedOops -Dapp.name=rhq-server -Xms1024M -Xmx1024M -XX:PermSize=256M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
4. It still uses the default as set in /bin/internal/rhq-server.sh file
Server heapsize is unaffected by changes made to rhqctl java opts
Per documentation, changing the min/max heap in the rhqctl will increase/decrease the heap size on the rhq server.
Moving to documentation component.
This is a bug in the documentation. The RHQ_CONTROL_JAVA_OPTS only applies to the rhqctl process and not that of any of the underlying JBoss ON components.
Additionally, modifications to the binary/launcher scripts is not supported and bug 1061311 had already been filed in that regard.
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
need to fail this. the jon 3.3 doc is not yet delivered.
(In reply to Larry O'Leary from comment #1)
> Moving to documentation component.
> This is a bug in the documentation. The RHQ_CONTROL_JAVA_OPTS only applies
> to the rhqctl process and not that of any of the underlying JBoss ON
> Additionally, modifications to the binary/launcher scripts is not supported
> and bug 1061311 had already been filed in that regard.
What would be the correct parameter to instruct users to change here? Would it be RHQ_SERVER_JAVA_OPTS (following the existing nomenclature), or JAVA_OPTS, or another parameter?
Thanks for your help
For UNIX/Linux, the appropriate environment variable is RHQ_SERVER_JAVA_OPTS and it should be set in rhq-server-env.sh.
Ready for review.