Clarity: Background Log Error Message OutOfMemoryError GC overhead limit exceeded

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Description:

The Background Log file is generating many error messages as shown below. How do we resolve this issue?

 	ERROR 2013-02-28 18:48:00,365 [Dispatch pool-4-thread-1 : bg@localhost
 	(tenant=clarity)] niku.blobcrack (clarity:none:none:none) Exception during blobcrack process java.lang.OutOfMemoryError: 
          GC overhead limit exceeded

Solution:

The error message can occur for other pages or functionality within Clarity as well. The portion of the message to focus is regarding the GC overhead limit.

This can be resolved by adding / appending the following parameter to the JVM parameters defined in the Clarity System Administration (CSA) application for both the Application and Background Services configurations.

 	-XX:-UseGCOverheadLimit 

This will force the application to use the full Garbage Collection (GC) overhead, if needed. After saving this configuration change, restart all services.

Keywords: CLARITYKB, how-to, configuration.

Environment

Release: ESPCLA99000-12.1-Clarity-Extended Support Plus
Component:

Resolution

.