Bug 1095805 - Changing Heapsize on JBoss ON Server doesn't work per the doc steps
Summary: Changing Heapsize on JBoss ON Server doesn't work per the doc steps
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Documentation
Version: JON 3.2
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: JON 3.3.0
Assignee: Jared MORGAN
QA Contact: Mike Foley
Jared MORGAN
URL:
Whiteboard:
Keywords: Documentation, EasyFix
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-08 14:49 UTC by dsteigne
Modified: 2018-12-05 18:29 UTC (History)
4 users (show)

(edit)
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.
Clone Of:
(edit)
[Admin_Config] Ready for review.
Last Closed: 2014-12-11 14:00:36 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 878843 None None None Never
Red Hat Bugzilla 1061311 None None None Never

Internal Trackers: 1061311

Description dsteigne 2014-05-08 14:49:51 UTC
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):
3.2.1

How reproducible:
Always

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

Actual results:
Server heapsize is unaffected by changes made to rhqctl java opts

Expected results:
Per documentation, changing the min/max heap in the rhqctl will increase/decrease the heap size on the rhq server.

Additional info:

Comment 1 Larry O'Leary 2014-06-05 16:32:34 UTC
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.

Comment 2 Simeon Pinder 2014-07-31 15:52:40 UTC
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993

Comment 3 Mike Foley 2014-08-05 20:36:08 UTC
need to  fail this.  the jon 3.3 doc is not yet delivered.

Comment 4 Jared MORGAN 2014-10-22 02:46:40 UTC
(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
> components.
> 
> Additionally, modifications to the binary/launcher scripts is not supported
> and bug 1061311 had already been filed in that regard.

Hey Larry, 

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

Jared

Comment 5 Larry O'Leary 2014-10-22 14:31:51 UTC
For UNIX/Linux, the appropriate environment variable is RHQ_SERVER_JAVA_OPTS and it should be set in rhq-server-env.sh.

Comment 7 Jared MORGAN 2014-11-07 03:48:35 UTC
Ready for review.


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