SAP Knowledge Base Article - Preview

2962015 - RS crashing with signal 4 and core dump - SAP SRS

Symptom

RS crashed due the following stack trace:

ERROR #1027 DSI EXEC(129(3) xxx.yyyy) - eneric/dsi/dsiutil.c(451)
 Open Client Client-Library error: Error: 16843058, Severity 5 -- 'ct_dynamic(): user api layer: external error: The connection has been marked dead.'.
ERROR #5275 DSI EXEC(129(3) xxx.yyyy) - eneric/dsi/dsiutil.c(481)
 The DSI thread could not make a connection to xxx.yyyy and configuration parameter dsi_non_blocking_commit is on. DSI will be restarted to prevent data loss.
ERROR #5275 DSI EXEC(129(3) xxx.yyyy) - /generic/useful/cm.c(9709)
 The DSI thread could not make a connection to xxx.yyyy and configuration parameter dsi_non_blocking_commit is on. DSI will be restarted to prevent data loss.
Thread DSI EXEC(129(3) xxx.yyyy) infected with signal 4.
Dumping context structure:
...
...
Dumping memory trace.

***************STACK TRACE***************

*****thread DSI EXEC(129(3) xxx.yyyy)*******

exc__appDumpStack
exc_terminate
bsd_catch_signal

*****End of stack trace.****
Internal error. Attempting to produce a core file.


Read more...

Environment

SAP Replication Server (SRS) 16.0 SP03 PL07

Product

SAP Replication Server 16.0

Keywords

thread DSI EXEC infected with signal 4 exc__appDumpStack exc_terminate bsd_catch_signal CR 821744 CR821744 , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Bug Filed

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.