SAP Knowledge Base Article - Preview

2620913 - ASE infected with signal 11 (SIGSEGV) in functions com__exctnume_copy or $cold_subparams - SAP ASE and SDK for SAP ASE

Symptom

  • jConnect client connection terminates unexpectedly.
  • ASE errorlog contains an Infected with signal 11 (SIGSEGV) error with one of two different stack traces, in either com__exctnume_copy() or $cold_subparams
  • Stack trace header may indicate a previous error 12828
  • Stack traces reported in errorlog :
    • Current process (0xdf30263) infected with signal 11 (SIGSEGV)
      kernel Address 0xc0000000004b2320 (), siginfo (code, address)
      com__exctnume_copy

      comnb_numtonum
      srv_numtonum
      relop__retrocast_cnst
      relop__retrocast
      relop__sqlt
      ResRelOp
      Optimize
    • Signal 11 with cold_subparams & siginfo(code, address) the stack shows as:
      Current process (0x3e19051c) infected with signal 11 (SIGSEGV) ($cold_subparams+0x5a0), siginfo (code, address) = (2, 0x0000000000000118)
      lasterror = 12828 preverror = 0 transtate = 0
      $cold_subparams
      $cold_s_setupvar
      s_compile
      curs_compile_at_open
      $cold_s_execute
      sequencer
      tdsrecv_open
  • The Java stack may report with below Exception.

java.sql.SQLException: JZ006: Caught IOException: com.sybase.jdbc4.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed.
 at com.sybase.jdbc4.jdbc.ErrorMessage.createIOEKilledConnEx(ErrorMessage.java:1152)
 at com.sybase.jdbc4.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:1195)
 at com.sybase.jdbc4.tds.Tds.handleIOE(Tds.java:5340)
 at com.sybase.jdbc4.tds.Tds.handleIOE(Tds.java:5285)
 at com.sybase.jdbc4.tds.Tds.cancel(Tds.java:2519)
 at com.sybase.jdbc4.tds.Tds.cancel(Tds.java:2443)
 at com.sybase.jdbc4.jdbc.SybStatement.doCancel(SybStatement.java:1034)
 at com.sybase.jdbc4.jdbc.SybStatement.batchLoop(SybStatement.java:2362)
 at com.sybase.jdbc4.jdbc.SybStatement.sendBatch(SybStatement.java:2170)
 at com.sybase.jdbc4.jdbc.SybStatement.executeBatch(SybStatement.java:2128)
 at com.sybase.jdbc4.jdbc.SybStatement.executeBatch(SybStatement.java:2046)
 at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeBatch(SybPreparedStatement.java:2092)
 at com.sap.customer.mseb.TinyIntTest.main(TinyIntTest.java:59)

Note: Complete signal 11 stacktraces are attached.


Read more...

Environment

  • SAP Sybase Adaptive Server Enterprise 15.7
  • SAP Sybase Adaptive Server Enterprise 16.0
  • SAP Adaptive Server Enterprise SDK 15.7 prior to SP140
  • SAP Adaptive Server Enterprise SDK 16.0 SP02 prior to PL08
  • SAP Adaptive Server Enterprise SDK 16.0 SP03 prior to PL04
  • jConnect Client
  • Java
  • Connection property 'HOMOGENEOUS_BATCH=true'

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP Adaptive Server Enterprise SDK 16.0 ; Sybase Adaptive Server Enterprise Cluster Edition 15.7 ; Sybase SDK 15.7 ; Sybase Software Developer Kit 15.7

Keywords

CR811189, 811189, CR#811189, TINYINT, HOMOGENEOUS_BATCH, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  stack, registers , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-SDK , SDK , 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.