SAP Knowledge Base Article - Preview

2894930 - WORKER thread infected with signal 11 in ll_next and dist_delivery_seq - SRS


Replication Server crashed with Signal 11 followed by a stack trace:

Thread WORKER( ) infected with signal 11.
Dumping memory trace.
***************STACK TRACE***************
*****thread WORKER( )*******
(linux_dump_all_func_stack+0x32) [0x8d6170]
(dbg_dump_stack_noarg+0x31) [0x8fb55d]
(dbg_dump_stack+0x164) [0x8fc880]
(exc__appDumpStack+0x105) [0x6e5675]
(exc_terminate+0x20f) [0x6e9225]
(linux_catch_signal+0x26c) [0x54750c]
/lib64/ [0x7ffff74ff680]
(ll_next+0xa) [0x787952]
(dist_delivery_seq+0xa41) [0x916c91]
(RSTaskExec+0x168) [0x856be4]
(srv__start_function+0x1eb) [0xa4b2db]
/lib64/ [0x7ffff74f7dd5]
/lib64/ [0x7ffff5d8fb3d]
*****End of stack trace.****
Internal error. Attempting to produce a core file.



  • SAP Replication Server (SRS) 16 SP03 PL07 and up
  • SAP Adaptive Server Enterprise (ASE) 16.0 with Always-on Option (HADR)
  • SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite with High Availability Disaster Recovery (BHADR)


SAP Adaptive Server Enterprise 16.0 ; SAP Replication Server 16.0


CR820332, CR#820332, 820332, repserver, HADR, WORKER, parrallel_dist, stacktrace, SEGV, segmentation, storage, access, violation, fault, segfault, stacktrc , KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , 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.