Recommended Java heap memory settings in RSA Identity Governance & Lifecycle
Originally Published: 2020-03-19
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
Resolution
The calculations used to determine these values are in the startup file /etc/init.d/aveksa_server under the heading: # compute JAVA_OPTS based on total system memory..
RSA does not recommend modifying these settings but if they need to be modified, look for the following section in the /etc/init.d/aveksa_server file that tells you what to be aware of and how to make the changes.
# If memory values need to be increased above these levels set them as needed# Ensure any database needs for memory are not effected
# Uncomment out the line below with the necessary values.
# It is recommended to set Xms = Xmx
#JAVA_OPTS=""-Xms8192m -Xmx8192m -XX:MaxPermSize=2048m"
Please also keep in mind that increasing the heap size above 32 GB as mentioned above will likely decrease performance.
Related Articles
RSA Governance & Lifecycle Recommended Practices: Performance Checks Number of Views Recommended Oracle 19c Optimizer Settings for RSA Identity Governance & Lifecycle Number of Views RSA Governance & Lifecycle Recommended Practices: Collecting from Active Directory Number of Views Recommended Oracle 12.2.0.1 or 12.1.0.2 Proactive Bundle Patch October 2017 or later Optimizer Settings in RSA Identity Go… Number of Views RSA Governance & Lifecycle Recommended Practice: Non-Person Account Management - Work in progress Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) Supported On-Demand Authentication (ODA) SMS providers for use with RSA Authentication Manager 8.x Deploying RSA Authenticator 6.2.2 for Windows Using DISM
Don't see what you're looking for?
