Symptom
During the deployment with migration mode, the platform update pod was failed due to the database connection reset by peer error, the log as below
| ..... {"instant":{"epochSecond":1744679980,"nanoOfSecond":221372382},"thread":"main","level":"INFO","loggerName":"de.hybris.platform.core.Initialization","message":">>> Updating schema (and type system) ...","endOfBatch":false,"loggerFqcn":"org.apache.log4j.Category","contextMap":{"Tenant":""},"threadId":1,"threadPriority":5,"origin":"PLATFORM"}
{"instant":{"epochSecond":1744680202,"nanoOfSecond":318403171},"thread":"main","level":"ERROR","loggerName":"de.hybris.bootstrap.ddl.DefaultDbScriptsExecutor","message":"problem executing sql [reason: StatementCallback; SQL [INSERT INTO composedtypes16 (hjmpTS, createdTS, modifiedTS, TypePkString, OwnerPkString, PK, sealed, p_extensionname, p_autocreate, p_generate, InternalCode, p_defaultvalue, InheritancePathString, jaloClassName, ItemJNDIName, Singleton, p_jaloonly, p_dynamic, SuperTypePK, p_legacypersistence, p_systemtype, p_catalogitemtype, p_catalogversionattributequali, p_uniquekeyattributequalifier, aCLTS, propTS, InternalCodeLowerCase, removable, propertyTableStatus, ItemTypeCode, p_comparationattribute, p_localized, p_sourceattribute, p_targetattribute, p_sourcetype, p_targettype, p_sourcenavigable, p_targetnavigable, p_orderingattribute, p_localizationattribute, p_previewdisabled) VALUES ('0', CONVERT(VARCHAR(24),'2025-04-15 01:20:11.276',121), CONVERT(VARCHAR(24),'2025-04-15 01:20:11.276',121), '8796093087826', NULL, '8796181069906', NULL, 'meijerservices', '1', '1', 'CartGroupCart', NULL, ',8796093055058,8796094431314,
...... 1', currentValue = '2703', template = NULL WHERE serieskey = 'pk_82'; UPDATE numberseries SET hjmpTS = NULL, seriestype = '1', currentValue = '719', template = NULL WHERE serieskey = 'pk_83'; UPDATE numberseries SET hjmpTS = NULL, seriestype = '1', currentValue = '43234', template = NULL WHERE serieskey = 'pk_87'; UPDATE numberseries SET hjmpTS = NULL, seriestype = '1', currentValue = '7005', template = NULL WHERE serieskey = 'pk_91']; Connection reset by peer; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer
at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:107)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:73)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:82)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:82)
at org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1575)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:398)
at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:622)
at de.hybris.bootstrap.ddl.DefaultDbScriptsExecutor.executeBatch(DefaultDbScriptsExecutor.java:135)
... 41 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3806)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:2127)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:4476)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:4378)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeBytes(IOBuffer.java:4030)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeString(IOBuffer.java:4100)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatementBatch(SQLServerStatement.java:977)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtBatchExecCmd.doExecute(SQLServerStatement.java:943)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7620)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3916)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:268)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:242)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeBatch(SQLServerStatement.java:1856)
at de.hybris.platform.jdbcwrapper.interceptor.StatementWithJDBCInterceptor.lambda$executeBatch$28(StatementWithJDBCInterceptor.java:175)
at de.hybris.platform.jdbcwrapper.interceptor.recover.SQLRecoverableExceptionHandler.passThrough(SQLRecoverableExceptionHandler.java:93)
at de.hybris.platform.jdbcwrapper.interceptor.recover.SQLRecoverableExceptionHandler.get(SQLRecoverableExceptionHandler.java:51)
at de.hybris.platform.jdbcwrapper.interceptor.JDBCInterceptor.get(JDBCInterceptor.java:61)
at de.hybris.platform.jdbcwrapper.interceptor.StatementWithJDBCInterceptor.executeBatch(StatementWithJDBCInterceptor.java:175)
at de.hybris.platform.jdbcwrapper.StatementImpl.executeBatch(StatementImpl.java:476)
at org.springframework.jdbc.core.JdbcTemplate$1BatchUpdateStatementCallback.doInStatement(JdbcTemplate.java:582)
at org.springframework.jdbc.core.JdbcTemplate$1BatchUpdateStatementCallback.doInStatement(JdbcTemplate.java:568)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:383)
... 43 more
Caused by: java.net.SocketException: Connection reset by peer
at java.base/sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:425)
at java.base/sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:445)
at java.base/sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:831)
at java.base/java.net.Socket$SocketOutputStream.write(Socket.java:1035)
at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyOutputStream.writeInternal(IOBuffer.java:1334)
at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyOutputStream.write(IOBuffer.java:1327)
at java.base/sun.security.ssl.SSLSocketOutputRecord.deliver(SSLSocketOutputRecord.java:345)
at java.base/sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:1308)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:2121)
... 63 more
shutting down hybris registry..
|
Read more...
Environment
SAP Commerce Cloud V2
Keywords
SAP Commerce Cloud, DBA, PS, release, system update, SQL command, connection reset by peer, blockings, bad performance, support request. , KBA , CEC-SCC-CLA-ENV-EMG , Environment Management , 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.
SAP Knowledge Base Article - Preview