We have investigated regular OOMKilled for a SAP Commerce Cloud customer.
After investigation, it appears that the OOMkilled was due to very high memory thread stack memory allocation/deallocation that creates over the time RSS memory fragmentation. The thread name is "HandshakeCompletedNotify-Thread" and related to a known issue with TransportContext.finishHandshake(), see https://bugs.openjdk.org/browse/JDK-8246039.
HttpURLConnection is called by Gigya Java SDK for each request to Gigya service and this code calls TransportContext.finishHandshake() at the end of the connection.
GSRequest should not create a new connection for each request to Gigya service but uses Apache HTTPClient instead of HttpURLConnection with a connection pool.
We have investigated regular OOMKilled for a SAP Commerce Cloud customer.
After investigation, it appears that the OOMkilled was due to very high memory thread stack memory allocation/deallocation that creates over the time RSS memory fragmentation. The thread name is "HandshakeCompletedNotify-Thread" and related to a known issue with TransportContext.finishHandshake(), see https://bugs.openjdk.org/browse/JDK-8246039.
HttpURLConnection is called by Gigya Java SDK for each request to Gigya service and this code calls TransportContext.finishHandshake() at the end of the connection.
GSRequest should not create a new connection for each request to Gigya service but uses Apache HTTPClient instead of HttpURLConnection with a connection pool.