SAP Knowledge Base Article - Preview

3595375 - Intermittent connection failures to custom database in SAP Commerce Cloud

Symptom

Connection failures to custom database server occur intermittently in SAP Commerce cloud. Following errors can be seen in logs:

"loggerName": "com.xxx.xxx.handler.xxx",
  "message": "xxx Exception Message: Error retrieving database meta-data; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.",
  "thrown": {
    "commonElementCount": 0,
    "localizedMessage": "Error retrieving database meta-data; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.",
    "message": "Error retrieving database meta-data; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.",
    "name": "org.springframework.dao.DataAccessResourceFailureException",
    "cause": {
      "commonElementCount": 35,
      "localizedMessage": "Error while extracting DatabaseMetaData; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.",
      "message": "Error while extracting DatabaseMetaData; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.",
      "name": "org.springframework.jdbc.support.MetaDataAccessException",
      "cause": {
        "commonElementCount": 35,
        "localizedMessage": "The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.",
        "message": "The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection.",
        "name": "com.microsoft.sqlserver.jdbc.SQLServerException",
        "extendedStackTrace": [
          {
            "class": "com.microsoft.sqlserver.jdbc.SQLServerException",
            "method": "makeFromDriverError",
            "file": "SQLServerException.java",
            "line": 237,
            "exact": false,
            "location": "mssql-jdbc-11.2.3.jre17.jar",
            "version": "?"
          },
          {
            "class": "com.microsoft.sqlserver.jdbc.SQLServerConnection",
            "method": "executeCommand",
            "file": "SQLServerConnection.java",
            "line": 3876,
            "exact": false,
            "location": "mssql-jdbc-11.2.3.jre17.jar",
            "version": "?"
          },
          {
            "class": "com.microsoft.sqlserver.jdbc.SQLServerStatement",
            "method": "executeCommand",
            "file": "SQLServerStatement.java",
            "line": 268,
            "exact": false,
            "location": "mssql-jdbc-11.2.3.jre17.jar",
            "version": "?"
          },
          ......
          ,
        {
          "class": "org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory",
          "method": "createMetaDataProvider",
          "file": "CallMetaDataProviderFactory.java",
          "line": 78,
          "exact": false,
          "location": "spring-jdbc-5.3.39.jar",
          "version": "5.3.39"
        }
      ]
    },
    "extendedStackTrace": [ 
      {
        "class": "org.springframework.jdbc.core.simple.SimpleJdbcCall",
        "method": "execute",
        "file": "SimpleJdbcCall.java",
        "line": 198,
        "exact": false,
        "location": "spring-jdbc-5.3.39.jar",
        "version": "5.3.39"
      },
      {
        "class": "uk.co.xxx.xxx.dataprocessing.dao.impl.xxx",
        "method": "xxx",
        "file": "xxx.java",
        "line": 51,
        "exact": false,
        "location": "xxx.jar",
        "version": "?"
      },
      {
        "class": "com.xxx.etl.handler.xxx",
        "method": "handle",
        "file": "xxx.java",
        "line": 81,
        "exact": false,
        "location": "xxx.jar",
        "version": "?"
      }

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Read more...

Environment

All SAP Commerce Cloud versions

Product

SAP Commerce Cloud all versions ; SAP Commerce all versions

Keywords

SQLServerException, connection pool, JdbcTemplate , KBA , CEC-SCC-PLA-PL , Platform , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.