Introduction

This article explains how to resolve a GC overhead limit exceeded memory error that occurs during a 360Bind comparison task.

Environment

• Product: 360Suite
• Product version: all versions
• Database: all

Symptoms

• A 360Bind comparison task fails.
• The task log contains the error message below.

Error Message

GC overhead limit exceeded

Cause

During a comparison, documents are first exported using a Content Export task. The export result is stored as XML files in the Bind repository.

If one or more of these XML files are too large, the comparison task consumes more memory than is allocated to the Tomcat server, triggering this error.

Resolution

Two approaches can resolve this issue:

• Option 1 — Reduce the XML file size by applying export filters.
• Option 2 — Increase the Tomcat Java memory allocation.

Option 1 — Reduce the XML file size

Apply filters during the export task to reduce the amount of data written to the Bind repository XML files. Fewer objects in the export results in less memory required during comparison.

You can reduce the export scope by:

• using more restrictive prompt values, or
• setting up global or document-level filters in the export task.

Option 2 — Increase the Tomcat Java memory

Open the Tomcat configuration tool and raise the maximum memory pool value on the Java tab. The appropriate value depends on the size of the compared documents and the resources available on the host server. Restart the Tomcat service to apply the change.

Using the BOBJ-hosted Tomcat

1. Find the service name of the Tomcat instance running 360Suite. Open Windows Services, right-click the Tomcat service, and select Properties to view the service name.
   
2. Open a command prompt as administrator.
3. Navigate to the Tomcat \bin directory:

   cd <tomcat>\apache-tomcat-9.0.56\bin

4. Run the configuration tool, replacing <service_name> with the actual service name:
   • Tomcat 9: tomcat9w //ES//<service_name>
   • Tomcat 8: tomcat8w //ES//<service_name>
   Example: tomcat9w //ES//360Suite_Tomcat_For_BI_4.3
   
   
5. In the Tomcat configuration window, go to the Java tab and set a higher value in the Maximum Memory Pool field.
   
6. Restart the Tomcat service to apply the new memory value.