Troubleshooting: Maximum Heap Size Does Not Change for the RADIUS Server

Version Affected: All
 
 

Overview

After increasing the maximum heap size for the RADIUS server following SecureAuth's guide for increasing RADIUS memory, the change does not take effect. Running the following command still reports the old, smaller value:

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

For example, the default heap size may have been 1 GB, you increased it to 2 GB following the guide, but the command above still returns 1 GB. There are two distinct, unrelated causes for this:

• See Cause 1 - The virtual machine (VM) hosting RADIUS does not have enough physical RAM to allocate the increased heap size.
• See Cause 2 - A known product defect prevents the new value from being applied, tracked as RAD-812.

In this article

• Cause 1: Insufficient RAM on the RADIUS VM
• Cause 2: Known Defect (RAD-812)

Cause 1: Insufficient RAM on the RADIUS VM

The VM itself does not have enough RAM available to allocate the increased heap size you configured for RADIUS.

Resolution 1:

1. Power off the VM.
2. Increase the VM's RAM to an amount that comfortably accommodates the increased heap size you are setting for RADIUS.
3. Power the VM back on.
4. Run through the steps in the RADIUS memory guide again.

Cause 2: Known Defect (RAD-812)

Even with sufficient RAM available and the guide's steps followed correctly, the maximum heap size change may still not apply. This is a known issue in the RADIUS Server package, tracked under development ticket RAD-812.

Resolution 2:

There is no workaround for this defect at this time. It is expected to be resolved in an upcoming update to the RADIUS Server package — check with SecureAuth Support for the current fix status if this is blocking your deployment.

 

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.