What occurs when the Java Virtual Machine (JVM) heap for the Content Platform Engine runs out of available memory?
According to IBM's FileNet P8 Platform documentation on tuning JVM heap size, when the Content Platform Engine's JVM heap is exhausted, all processing running within that JVM stops. The JVM does not automatically restart itself, the engine does not restart on its own, and there is no mechanism for a JVM to borrow memory from other members of a cluster. This is precisely why IBM stresses proper heap sizing and garbage collection tuning for the Content Platform Engine — to prevent an out-of-memory condition from halting all in-flight processing.
Community Discussion