RSA Governance & Lifecycle no longer displays memory allocation on startup. 
2 years ago
Article Number
000072036
Applies To
  • RSA Governance & Lifecycle 8.0.0
Issue
RSA Governance & Lifecycle no longer displays memory allocation on startup. 
Cause
Due to changes in the way the services are started this information is no longer logged to the console. 
Resolution

 

 

Workaround

Detail information on the memory calculations arrived at during the startup of Governance & Lifecycle is now logged to /var/log/messages. 

In order to see the calculations done in itned for memory allocation restart acm (or stop and start acm) and then view the contents in /var/log/messages for the aveksa_server application.

Use the unix command "grep aveksa_server /var/log/messages" to see the details of the startup. 

Example:

 

acm-800:~ # acm restart
acm-800:~ # grep  aveksa_server /var/log/messages
...
2024-03-01T16:25:03.702692-05:00 acm-800 aveksa_server[19984]: Total Memory:   19937 MB
2024-03-01T16:25:03.702900-05:00 acm-800 aveksa_server[19984]: Reserved for OS: 2048 MB
2024-03-01T16:25:03.703031-05:00 acm-800 aveksa_server[19984]: Reserved by AFX: 4096 MB
2024-03-01T16:25:03.703140-05:00 acm-800 aveksa_server[19984]: Reserved by DB:  8965 MB
2024-03-01T16:25:03.703251-05:00 acm-800 aveksa_server[19984]: Reserved for Process and Host Controller: 1536 MB
2024-03-01T16:25:03.703357-05:00 acm-800 aveksa_server[19984]: Available for WildFly:3292 MB
2024-03-01T16:25:03.703461-05:00 acm-800 aveksa_server[19984]: Starting RSA Identity Governance and Lifecycle:
2024-03-01T16:25:03.703575-05:00 acm-800 aveksa_server[19984]: Verifying Oracle and System time match ...
2024-03-01T16:25:10.727329-05:00 acm-800 aveksa_server[19984]: Database : 03-01-2024 16:25:10 -0500     ~     Web : 03-01-2024 16:25:10 -0500
2024-03-01T16:25:11.897501-05:00 acm-800 aveksa_server[19984]: This system will start in Domain mode
2024-03-01T16:25:11.904007-05:00 acm-800 aveksa_server[19984]: Command to be issued:
2024-03-01T16:25:11.904243-05:00 acm-800 aveksa_server[19984]: '/home/oracle/wildfly/bin/domain.sh' -b 0.0.0.0 -Djboss.bind.address.management=192.168.26.170 -Djboss.bind.address.private=acm-800.vcloud.local  -Djboss.memory.max.heap.size=2798m -Djboss.memory.max.permgen.size=493m -Djava.awt.headless=true -Dclient.encoding.override=UTF-8 -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Daveksahome="/home/oracle" -DLog4jContextSelector=org.apache.logging.log4j.core.selector.BasicContextSelector
2024-03-01T16:25:12.388077-05:00 acm-800 aveksa_server[19984]: Done start of host controller
2024-03-01T16:26:41.584593-05:00 acm-800 aveksa_server[19984]: Waiting for RSA Identity Governance and Lifecycle to start.
2024-03-01T16:26:41.584899-05:00 acm-800 aveksa_server[19984]: RSA Identity Governance and Lifecycle is running ...
2024-03-01T16:26:41.585022-05:00 acm-800 aveksa_server[19984]:
acm-800:~ #
 
Notes
This information may be useful in understanding how the memory allocation is being calculated.  In general there is no requirement to fine tune these settings but this information may be useful in understanding why additional memory may be useful.