2154849 - ASE produces stacktrace and goes down or runs out of user connections - SAP ASE

• ASE errorlog reports a stack trace.
   
• On Windows platform:
   

• the stack trace includes the function longjmp() among others:

RtlRaiseStatus()
RtlIsDosDeviceName_U()
RtlUnwindEx()
longjmp()

• ASE can go down afterwards.

• On Unix platforms:
   

• ASE report signal 4 (SIGILL) at the module mda__get_total_sync_commit_time() with an incomplete stack trace:

Current process (0x3f0020) infected with signal 4 (SIGILL)
Address hex# (mda__get_total_sync_commit_time+0x252)

• There can be many instances of the stack trace
• Which can be followed, after some time, by (many) instances of error 1601:

Error: 1601, Severity: 17, State: 3
There are not enough 'user connections' available to start a new process. Retry when there are fewer active users, or ask your System Administrator to reconfigure ASE with more user connections.

SAP Adaptive Server Enterprise (ASE) 16.0

kisignal, RtlRaiseStatus, RtlIsDosDeviceName_U, RtlUnwindEx, CreateFiberEx, periodic, crash, message, monState, CR778553, CR#778553, 778553 , KBA , longjmp , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Bug Filed