When running intensive DB operations such as data imports or synchronization jobs, after a long period of time Java heap memory usage increases and is never released. The import or sync job will run for a long time without much progress and a lot of CPU time will be spent doing garbage collection. It may result in an OutOfMemoryError and the node becoming unresponsive.
When taking thread dumps, you will likely see the "Finalizer" thread BLOCKED with a stack trace related to the DB Driver:
"Finalizer" #3 daemon prio=8 os_prio=0 cpu=60210.00 [reset 60210.00] ms elapsed=8670.72 [reset 8670.72] s allocated=68480 B (66.88 KB) [reset 68480 B (66.88 KB)] defined_classes=1
If you take a heap dump you will notice the largest object by retained size is of class java.lang.ref.Finalizer and many of the classes contained in the heap dump are related to the HANA DB Driver (com.sap.db.jdbc.*)
Hybris Commerce 6.x
SAP Commerce 1808+
HANA, OutOfMemoryException, OutOfMemoryError , KBA , CEC-COM-CPS , SAP Commerce , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.