Okta Access Gateway Generates a Java Heap Space Out of Memory Error

The Okta Access Gateway (OAG) Admin UI becomes sluggish or slow when the OAG admin service runs out of memory. Administrators can resolve this issue by upgrading OAG to version 2024.6.1 or later, or by increasing the maximum heap memory assigned to the Admin Service. When this issue occurs, the Admin UI and logs display the following error messages.

Server Side Error occurred
Server side exception has been logged.
Please notify support.

The Okta Access Gateway Admin UI displays the server-side error message as shown in the following image.

2023-08-03T03:12:55.000-07:00 localhost ACCESS_GATEWAY WEB_CONSOLE handleExceptions
2023-08-03T03:12:55.000-07:00 localhost org.springframework.web.util.NestedServletException Handler dispatch failed; nested exception is java.lang.OutOfMemoryError: Java heap space

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Access Gateway (OAG)
• Access Gateway Admin Service
• Admin UI

The Okta Access Gateway admin service lacks sufficient heap memory, causing it to run out of memory and perform poorly.

How does an administrator resolve the Java heap space out of memory error in Okta Access Gateway?

Upgrade Okta Access Gateway to version 2024.6.1 or later, or increase the maximum memory assigned to the Admin Service from the Management Console.

• Upgrade Okta Access Gateway to version 2024.6.1 or later. Starting in version 2024.6.1, Okta increases the default maximum heap memory for the Admin Service from 256 MB to 512 MB.
• If the issue persists in version 2024.6.1 or newer, increase the maximum memory assigned to the Admin Service in the Okta Access Gateway Management Console by following the steps in the Access Gateway Admin documentation.
• Contact Okta Support for assistance with evaluating the size of memory to assign or if upgrading to version 2024.6.1 or later is not possible.