While reviewing the application logs, many "SQL search error - The connection is closed" errors are observed.
Using the Visualize tool in Kibana and creating buckets for logs.thread.keyword and kubernetes.pod_name.keyword, you find that the error is only observed on a single thread per pod. It may happen that more than one thread is affected per pod, but it will be evident from the chart that these threads are in the minority.
Taking one of the results above, you can filter for the specific pod and thread when searching for "SQL search error - The connection is closed" to determine the time of its first occurrence.
Similarly, you may do the same when searching for "SQL search error - Connection reset" and find that the time of its first occurrence was only a few seconds earlier.
If the hac web application is configured on the affected aspect, debug-level logging on the de.hybris.platform.jdbcwrapper.ConnectionImpl class can be enabled during runtime. This is not a required step in identifying the problem, but it is used here to illustrate more clearly the inconsistency between the physical and logical (pooled) connections.
For this to have the desired effect, it would need to be enabled on the exact pod where the errors were identified.
Once the above is enabled, the logs will start showing additional information along with the error when it resurfaces. For every occurrence of the "connection is closed" error, the value of closed will be false.
SAP Commerce Cloud
hybris,db,jdbc,pool,sql,leak , KBA , CEC-COM-CPS-COR , SAP Commerce Core , 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.