If you look at the args in the older post you linked, you'll see that the RAM commitment for the service is called as a variable (
Michael J. Rogers
Subject: |
RE: Zenoss 6.3.2 - Unable to load the visualization library |
Author: |
Gerald Müller |
Posted: |
2020-07-09 02:53 |
Hi Michael,
thanks, that is also what I did, please find below the error message I got during service-start:
"Error occurred during initialization of VM
Initial heap size set to a larger value than the maximum heap size"
Thanks
------------------------------
Gerald Müller
------------------------------
Subject: |
RE: Zenoss 6.3.2 - Unable to load the visualization library |
Author: |
Gerald Müller |
Posted: |
2020-07-10 02:34 |
Hi Michael,
wanted to let you know I gave it another try and set the parameter back to environment=(JVM_ARGS="-Xmx{{bytesToMB .RAMCommitment}}m"
)
This time CentralQuery service started without issues, I tried with different values for RAM commitment but the error message "Initial heap size set to a larger value than the maximum heap size" is not reproduceable anymore. This is a very interesting behaviour, do you know if the parameters used for startup are documented anywhere in the logs?
Thanks again,
Gerald
------------------------------
Gerald Müller
------------------------------