SAP Knowledge Base Article - Preview

3112081 - Signal 11 (SIGSEGV) in STSendMsgs() - SAP ASE 16.0 with HADR

Symptom

  •  Client connection unexpectedly terminated.
  • The ASE errorlog contains an "infected with signal 11" error with an "Address:" line showing the function STSendMsgs():

Current process (0x0) infected with signal 11 (SIGSEGV)
Current Process is running on a Non-Engine Thread
Address 0x0x00007f331af7d61a (STSendMsgs+0x3a2), siginfo (code, address) = (1, 0x0x0000000000000eb8)

  •  The erorr is followed by a stack trace that includes these functions:

STSendMsgs
ubcWaitForCompletion
undo_blockingcall_thread
ra_ci_send_CI_message
ra_ci_send_mode_switch_message
ra__ci_background_task_wait_for_srs_ack
ra__ci_background_task

  along with the message:

Blocking call executing on behalf of xxxxxxx failed with exception.

Note: A complete stack trace is available under Attachments.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE)  16.0
  • SAP Replication Server (SRS) 16.0
  • High Availability Disaster Recovery (HADR)

Product

SAP Adaptive Server Enterprise 16.0

Keywords

Sybase, infected, signal, SEGV, SIGSEGV, segment violation, storage access violation, kisignal, CR#825255, CR825255, 825255
 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (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.