Web UI crashes due to java.lang.OutOfMemoryError: Java heap space
search cancel

Web UI crashes due to java.lang.OutOfMemoryError: Java heap space

book

Article ID: 218400

calendar_today

Updated On:

Products

CA Workload Automation DE

Issue/Introduction

Users are unable to access the Web Client to monitor batch. The service was found to be down.

Environment

Release : 12.2 and 12.3

Component : CA WORKLOAD AUTOMATION DE (DSERIES) WEB CLIENT

Cause

[ERROR] [ <https-jsse-nio-8443-exec-23> ] [28 jun; 09:49:11.856] org.springframework.boot.context.web.ErrorPageFilter Forwarding to error page from request [/dewebui/api/monview/definition/list] due to exception [Handler dispatch failed; nested exception is java.lang.OutOfMemoryError: Java heap space]
org.springframework.web.util.NestedServletException: Handler dispatch failed; nested exception is java.lang.OutOfMemoryError: Java heap space

Resolution

By default, java heap is set to 4GB max in the catalina.bat|catalina.sh script on the Web Client server.

On Windows:

  1. Navigate to <DE_WEB_CLIENT_INSTALLATION_DIRECTORY>\apache-tomcat\bin directory.
  2. Open catalina.bat for editing.
  3. Look for JAVA_OPTS="-Xmx4096m -XX:OnOutOfMemoryError="
  4. Increase memory setting by double. JAVA_OPTS="-Xmx8192m -XX:OnOutOfMemoryError="
    Note:
    Maximum java heap allowed is 16GB.
  5. Save the file.
  6. Restart Web Client services.

On UNIX/Linux:

  1. Navigate to <DE_WEB_CLIENT_INSTALLATION_DIRECTORY>/apache-tomcat/bin directory.
  2. Open catalina.sh for editing.
  3. Look for JAVA_OPTS="-Xmx4096m -XX:OnOutOfMemoryError="
  4. Increase memory setting by double. JAVA_OPTS="-Xmx8192m -XX:OnOutOfMemoryError="
    Note:
    Maximum java heap allowed is 16GB.
  5. Save the file.
  6. Restart Web Client services.

Additional Information

  • The maximum amount of memory that can be allocated to Web Client is 16GB.
  • Maximum number of users that can access Web Client at one time is 50.
    If there is a need for more than 50 users accessing the Web Client at one time, you should stand up another Web Client instance.
  • Each user should have their own user account and not be sharing an account.
  • Multiple users using the same account is a security violation/risk and can also lead to performance issues.
  • Multiple subscriptions to the same workload can cause performance issues.