CQ5 Author or Publisher instance is down due to OutOfMemoryError.

Overview

OutOfMemoryError can occur any time in heap due to insufficient heap memory being available for new Java objects creation. CQ Author/Publisher will eventually crash due to OutOfMemoryError and would need to be restarted.

  

Issue

CQ5 Author or Publisher instance is down due to OutOfMemoryError.

Resolution

1.     

2.    Access all publisher and author instances and note which all instances are not responding. 

 

3.      For all instances not responding Access CRX error logs Note down which all instances are throwing OutOfMemoryError. In error log OutOfMemoryError can be searched by searching file content for string ”OutOfMemoryError”

4.    For every publisher instance throwing OutOfMemoryError follow the below steps: 

5.      Execute Datastore Garbage Collection operation in configuration repository.  To execute this operation visit http://:/system/console/memoryusage for the publisher instance and click on runDataStoeGarbageCollection operation as shown below.

6.    This should free up some memory.

7.    Stop the server by executing

8.    Start the server by executing

9.    Access the publisher instances and note which all publishers are not responding.

10. If all publishers instances are responding well issue is resolved.