2651690 - CIS "idle connection timeout " setting can cause Signal 11s in connectivity routines - SAP ASE

• Connections to the ASE may end unexpectedly
• And the ASE may also shutdown unexpectedly.
• The ASE errorlog contains "infected with signal 11" messages along with stacktraces, for example:

Current process (0x250013) infected with signal 11 (SIGSEGV)
Address 0x0x00000000019767a3 (np_conn_props+0x173), siginfo (code, address) = (1, 0x0x000000000000008c)

• Stack traces include any of the following functions:

np_conn_props
ct_poll
kctCheckAsync
omni_ct_cancel
hk_cis_idle_timeout
omni_ct_send
ct__mp_free
pthread_mutex_lock

  Note: A complete stack trace is available under Attachments.

• Sometimes timeslice messages are reporetd as well, for example:

timeslice -501, current process infected at 0x366fce0dbe ((null)+0x366fce0dbe)

• Other messages in the ASE errorlog may be:
   
• Restarted process 'HK CHORES'
• usctclose(CS_FORCE_CLOSE) returns CS_FAIL
• RDESDISC, spid <number> rdesp <hex number> rd_connection <hex number>: usctcondrop failed.
• Run to completion task 'CtlibController' exiting.

Read more...

• SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0
• SAP Adaptive Server Enterprise Cluster Edition (ASE CE) 15.7 and 16.0
• Component Integration Services (CIS)

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition ; SAP Adaptive Server Enterprise 16.0 ; SAP Adaptive Server Enterprise 16.0 Cluster Edition ; Sybase Adaptive Server Enterprise Cluster Edition 15.7

Sybase, ASEServer, SAPASE, dataserver, CR815204, CR#815204, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, registers, 815204 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Bug Filed