2878508 - Error 60036 and Signal 11 in mem_memFree() when dropping a connection or purging a queue - SRS

• Execution of the command "drop connection" to standby database fails with Error 60036:

1> drop connection to STANDBY_ASE.DB_NAME
2> go
Msg 60036, Level 12, State 0:
Server 'REP_SERVER_NAME':
Failed to acquire lock on sync element 'UNKNOWN'. Info 21.

• Same problem can also happens when trying to purge the queue manually with command "sysadmin sqm_purge_queue".
• This usually happens when there is large stable device(s), and it contains a lot of data.
• A Signal 11 error with a stack trace is also printed in the errorlog:

Thread GLOBAL RS(GLOBAL RS) infected with signal 11.
Dumping memory trace.
STACK TRACE
thread GLOBAL RS(GLOBAL RS)
REP-16_0binrepserver(linux_dump_all_func_stack+0x32) [0x8d5240]
REP-16_0binrepserver(dbg_dump_stack_noarg+0x31) [0x8fa62d]
REP-16_0binrepserver(dbg_dump_stack+0x164) [0x8fb950]
REP-16_0binrepserver(exc__appDumpStack+0x15e) [0x6e4dce]
REP-16_0binrepserver(exc_terminate+0x20f) [0x6e8925]
REP-16_0binrepserver(linux_catch_signal+0x26c) [0x54731c]
lib64libpthread.so.0(+0xf5d0) [0x7ff98f04e5d0]
REP-16_0binrepserver(mem_memFree+0x10) [0x79335a]
REP-16_0binrepserver(srv_free+0x19) [0xa19ed9]
REP-16_0binrepserver(srv__freermtpwd+0x3d) [0xa4167d]
REP-16_0binrepserver(srv_termproc+0x250) [0xa36470]
REP-16_0binrepserver(srv__start_function+0x212) [0xa4a2b2]
lib64libpthread.so.0(+0x7dd5) [0x7ff98f046dd5]
lib64libc.so.6(clone+0x6d) [0x7ff98d8df02d]
End of stack trace.
Internal error. Attempting to produce a core file

• SAP Replication Server (SRS) 16.0
• SAP Open Client/Server (OCS) 16.0

repserver, CR#820821, 820821, CR820821, CR#820834, 820834, CR#820834, SEGV, segmentation, storage, access, violation, fault, segfault, stacktrace, stacktrc , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Bug Filed