Maximum Heap Size is not changing after increasing on RADIUS server

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  [All]


    After increasing the maximum heap size from the steps in the guide, upon checking the maximum heap size using the following command:

    java -XX:+PrintFlagsFinal -version | findstr /i "MaxHeapSize" 

    You'll notice that the maximum heap size output has not changed. For instance, the default size may have been 1 GB initially but you allocated for 2 GB and the output is still returning as 1 GB.



    Check that the RAM on the VM itself has enough to allocate for the size you are increasing to for RADIUS.



    Power off the VM and increase the amount of RAM so it has an adequate amount to accommodate for the increased heap size you are setting for RADIUS. Once you have increased the RAM, power the VM back on and run through the steps in the guide once more.


    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.