Error: "java.lang.OutOfMemoryError: GC overhead limit exceeded" when attempting to mark incidents for deletion

Products

• Data Loss Prevention
• Data Loss Prevention Enforce

Issue/Introduction

You create a job to delete incidents older than 18 months, System > Incident Deleter > Flag Incidents For Deletion.

When the job is run, it fails within five minutes.

The localhost log has the following entries:

 

Source: org.quartz.core.JobRunShell

Message: Job FLAG_INCIDENTS_DELETION_JOB_EXEC.FLAG_INCIDENTS_DELETION_JOB threw an unhandled Exception: 

Cause:

java.lang.OutOfMemoryError: GC overhead limit exceeded

 

Source: org.quartz.core.ErrorLogger

Message: Job (FLAG_INCIDENTS_DELETION_JOB_EXEC.FLAG_INCIDENTS_DELETION_JOB threw an exception.

Cause:

org.quartz.SchedulerException: Job threw an unhandled exception.org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.OutOfMemoryError: GC overhead limit exceeded]

at org.quartz.core.JobRunShell.run(JobRunShell.java:224)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)

Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded

 

java.lang.OutOfMemoryError: GC overhead limit exceeded

Cause

The job identified over 1.4 million incidents to be marked for deletion.

Resolution

In the SymantecDLPManager.conf file, increase the "wrapper.java.maxmemory = 4096" to "wrapper.java.maxmemory = 8192".
After increasing the max java heap in the SymantecDLPManager.conf file, the job was able to complete.

Another recommendation is to decrease the amount of incidents to mark for deletion in any one job.