2984475 - Signal 11 in _ci_log_message_task() for CI Logger crashes RepServer - SRS 16.0

• After multiple CI Logger errors:

E. 2020/10/23 12:00:13. ERROR #85 CI Logger( ) - ric/ci/spqplogfile.c(2280)
       Attempting to read SPQ log file '/var/opt/sybase/SPQ/.../SPQ_4.dat' beyond what is verified as written (reader offset = 298300276, current offset = 698780036, size = 94).
E. 2020/10/23 12:00:13. ERROR #85 CI Logger( ) - eric/ci/spqpreader.c(476)
       Failed to traverse the SPQ log file '/var/opt/sybase/SPQ/.../SPQ_4.dat'.
E. 2020/10/23 12:00:13. ERROR #85 CI Logger( ) - eric/ci/spqpreader.c(251)
       SPQ 'MYDB' could not fulfill request for message 5207402, because the message is not found.

• The SPQ Reader closed and Consumer Reader exited for the MYDB database:

I. 2020/10/23 12:00:14. Close the SPQ Reader(33554432) at index 5206734 for the SPQ 'MYDB'.
W. 2020/10/23 12:00:14. WARNING #85 CI Logger( ) - generic/ci/msgcsum.c(3757)
Consumer Reader(MYDB:33554432) will exit because it failed to read a message(errcode = 411).

• Then SRS reported an "infected with signal 11" error in the CI Logger thread and crashed with a core dump:

T. 2020/10/23 12:00:14. (12): Thread CI Logger( ) infected with signal 11.
T. 2020/10/23 12:00:14. (12): Dumping memory trace.
T. 2020/10/23 12:00:14. (12): ***************STACK TRACE***************
T. 2020/10/23 12:00:14. (12): *****thread CI Logger( )*******
T. 2020/10/23 12:00:14. (12): (linux_dump_all_func_stack+0x32) [0x8d6c80]
T. 2020/10/23 12:00:14. (12): (dbg_dump_stack_noarg+0x31) [0x8fc53d]
T. 2020/10/23 12:00:14. (12): (dbg_dump_stack+0x164) [0x8fd860]
T. 2020/10/23 12:00:14. (12): (exc__appDumpStack+0x105) [0x6e5dd5]
T. 2020/10/23 12:00:14. (12): (exc_terminate+0x20f) [0x6e9985]
T. 2020/10/23 12:00:14. (12): (linux_catch_signal+0x26c) [0x5476bc]
T. 2020/10/23 12:00:14. (12): /lib64/libpthread.so.0(+0x11c00) [0x7ff4750a0c00]
T. 2020/10/23 12:00:14. (12): /lib64/libc.so.6(+0x7db99) [0x7ff473713b99]
T. 2020/10/23 12:00:14. (12): (_ci_log_message_task+0x78) [0x5685a8]
T. 2020/10/23 12:00:14. (12): (RSTaskExec+0x168) [0x8576e4]
T. 2020/10/23 12:00:14. (12): (srv__start_function+0x1eb) [0xa4c56b]
T. 2020/10/23 12:00:14. (12): /lib64/libpthread.so.0(+0x96da) [0x7ff4750986da]
T. 2020/10/23 12:00:14. (12): /lib64/libc.so.6(clone+0x6d) [0x7ff47378627d]
T. 2020/10/23 12:00:14. (12): *****End of stack trace.****
T. 2020/10/23 12:00:14. (12): Internal error. Attempting to produce a core file.

• About 1.5 hours after SRS restarted, CI Logger errors for the MYDB database resurfaced. There was no SRS crash yet. 
• These CI Logger errors were reported for the MYDB database often (almost every day) since SRS was booted about a month ago. However, SRS never crashed until now. 

• SAP Replication Server (SRS) 16.0
• SAP Adaptive Server Enterprise (ASE) 16.0 with Always-on Option (HADR)
• High Availability Disaster Recovery (HADR) with external replication
• Linux on x86_64 64bit

CR823282, CR#823282, 823282, stream, streaming, spq_data_file_size, suspend, resume, SQP, Agent, spq_agent, capture , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Bug Filed