Tomcat memory issue

Tomcat memory issue

Symptoms

  1. Relevant information: Error about memory issue in a 360Suite task
  2. Error message(s): "java.lang.OutOfMemoryError: GC overhead limit exceeded"
  3. Information location: Visible in the task logs and / or the tomcat logs

Environment

Product: 360Suite

Resolution

In order to resolve, you have to increase the amount of memory allocated to the 360Suite tomcat.
 

Windows environment 

This has to be done in the Tomcat Configuration tool. 

This tool can be found in the 360Suite installation folder (next to the apache-tomcat folder) if you are using the tomcat we deliver with 360Suite.
In other cases (third-party tomcat or BOBJ tomcat), this tool is also available because it is installed alongside the tomcat itself. It should be accessible via the Windows start menu.
  1. Open the Tomcat Configuration as Administrator
  2. Go to the Java tab
  3. In the Maximum memory pool section you can change the maximum amount of memory allocated to the tomcat (this adjustment must be done according to the server memory capacity)
  4. Click “apply” then restart the tomcat 


Linux environment

On a Linux server, the memory settings for Apache Tomcat can be added or modified in the file where the environment variables are configured.

Typically, in <apache-tomcat>/bin/setenv.sh or another “.sh” file (in the bin directory) that is used by default to start the tomcat. Several parameters for the memory values can be set here but the most important is -Xmx that defines the maximum memory size. It can be set with either a megabytes value (m) or a gigabytes value (g)

Example : 
CATALINA_OPTS="-Xms4g -Xmx12g -Xss-256k"

JAVA_OPTS="$JAVA_OPTS -XX:MaxmetaspaceSize=1024m"

For more details about this Linux Tomcat configuration, please refer to the offical Apache Tomcat documentation.
A Tomcat restart is necessary after this change.

    • Related Articles

    • 360Suite database configuration is not set when restarting Tomcat server

      Symptoms On application startup, a warning popup appears In the Administration console, the database configuration is empty even though is was setup previously Environment 360Suite Web Platform Linux server (all) Additional symptoms : tomcat logs In ...

    • What are the proper steps to set up the Tomcat service account for Web Platform?

      Symptom How to configure 360Suite Web Platform to use a Windows domain service account to run the 360Suite Windows Service, if it is not an Administrator on the server, i.e. the Tomcat user? Environment 360Suite Web Platform Cause The issue is ...

    • Change Tomcat after 2025.1 upgrade

      Context To prepare for BI 2025 moving away from Java 8, we migrated from Java 8 to Java 21. This migration impacts everyone doing update from previous version, as the version used for Tomcat is not compatible anymore, as Java 21 requires a Tomcat 10 ...

    • How to fix the 'WEAK link' issue

      Symptom How to relink a document to a universe when encountering a "weak link" issue? Environment 360Eyes SAP BusinessObjects Enterprise XI 3.1 SAP BusinessObjects Business Intelligence 4.0 SAP BusinessObjects Business Intelligence 4.1 SAP ...

    • Read Tomcat Logs after 2025.1 upgrade

      Context 2025.1 made a lot of changes regarding log generation. Allowing users and support agent to be more efficient in the search of issues. The 360Suite Tomcat will now generate new files if old one are getting too large, this will only happen on ...