Endeca Tools and Framework IFCR log with Heap size issue - Endeca Tools and Framework

IFCR Log:
12.02.2016 16:23:51.770 *ERROR* [10.49.186.35 [1455311472252] POST /ifcr/system/endeca/sitePromoter HTTP/1.1] org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to read property state: 1ad8274a-706a-46cd-bc0c-51866b5fe27f/{http://www.jcp.org/jcr/1.0}data java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.

12.02.2016 09:34:30.995 *ERROR* [10.49.186.35 [1455285129628] POST /ifcr/system/endeca/sitePromoter HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught Throwable java.lang.OutOfMemoryError: Java heap space
12.02.2016 09:34:50.576 *ERROR* [http-8006-26] org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in Thread Thread[http-8006-26,5,main] java.lang.NullPointerException        at java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:190)    


Solution:
In Workbench 3.1.x or 11.x (within Endeca Tools and Frameworks), the setting can be modified by editing the -Xmx value in $ENDECA_TOOLS_ROOT/server/bin/workbench.sh

- Default Setting is 1 GB and you can increase it to 2 GB or as required.

# Prepend WB_CATALINA_OPTS to standard Workbench CATALINA_OPTS
CATALINA_OPTS="${WB_CATALINA_OPTS} -Xms256m"
CATALINA_OPTS="${CATALINA_OPTS} -Xmx2G"

After making this change the Workbench must be stopped and restarted for the change to take affect.