igort Trusted Contributor.
Trusted Contributor.
295 views

(OO) Support Tip: Heap size settings in OO containers (in container. HCM) prior to version 1017.11

In OO containers prior to HCM 2017.11, the

OO_CENTRAL_JAVA_INITMEMORY

OO_CENTRAL_JAVA_MAXMEMORY

 

settigs in hcm-oo.yaml  file (in “/var/vols/itom/core/suite_install/hcm/output” folder) were not taken into account.

 

Even if the maximum heap size was set here e.g. to 4GB and the following was performed:

kubectl delete -f hcm-oo.yaml

kubectl create -f hcm-oo.yam

 

OO wrapper.log would still show:

INFO   | jvm 1    | 2018/05/17 06:37:19 | INFO: Command line argument: -Xmx1024m

 

 

Obviously, the best option here is to use the latest HCM version where this is fixed (and multiple other improvements are introduced).

 

However if the old version needs to be used, it can be worked around e.g by adding the following line into hcm-oo.yaml (this is a sample manipulation, the regex can be adjusted as needed):

           command:

            - "/bin/sh"

          args:

            - "-c"

            - >

                sed -i -e s/memory=1024/memory=4096/ /usr/local/hpe/oo/central/conf/central-wrapper.conf &&

                rm -f /usr/local/hpe/cluster_conf/database.properties &&

                /usr/bin/oo-central-startup.sh

 

 

(and of course again:

kubectl delete  –f hcm-oo.yaml

kubectl create –f hcm-oo.yaml)

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.