Communications Session Manager crashes frequently using Avaya Interaction Center CTI Driver for Siebel (Doc ID 1598899.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CTI - Version 8.1.1.9 [23016] to 8.2.2.4 SIA [23030] [Release V8]
Information in this document applies to any platform.

Symptoms

Customer observed sporadically Communications Session Manager component crashes in Production using CommSessionMgr component running over AIX 6.1 platform.

The behavior could not be reproduced in lower environment and is very sporadically such as  multiple crash on the same day and sometimes no crashes for a couple of days.

Most of the time no crash.txt file is generated and only a core file in Siebel Server BIN folder.

Siebel Enterprise Server log shows:

ServerLog ProcessExit 1 0002c3cd51fb00f8:0 2013-08-06 19:05:53 CommSessionMgr 18350264 SBL-OSD-02006   Process 18350264 exited with error - Process exited because it received signal SIGABRT.

Analisys made over the core files as per Document 477520.1 "How To Troubleshoot Siebel Server Component Crashes on UNIX" reveal the following consistently call stack for every CommSessionMgr crash:

 

0xd0507f8c _p_raise+  0x000002e0
0xd0137284 raise+  0x000001d0
0xd01d5868 abort+  0x0000053c
0xd0628710 myabort__3stdFv+  0x00000070
0xd0627c70 terminate__3stdFv+  0x00000274
0xd0627b90 terminate__Fv+  0x00000088
<unnamed block>
0xd1359288 _Xran__Q2_3std12_String_baseCFv+  0x00000250
0xd1352b50 erase__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__FUlT1+  0x000003b8
0x3286bb38 rollLogFiles__FPv+  0x00002588
0xd04f0c50 _pthread_body+  0x00000468

OR running dbx over the core file:

/crashfiles $ dbx -p ./pathmap ./siebmtshmw core.15400994.19155406
Type 'help' for help.
[using memory image in core.15400994.19155406]
reading symbolic information ...warning: Unable to access the stab file. Some info may not be available
IOT/Abort trap in pth_signal.pthread_kill [./usr/lib/libpthread.a] at 0xd0508b20 ($t508)
0xd0508b20 (pthread_kill+0xa0) 80410014         lwz   r2,0x14(r1)

(dbx) where
pth_signal.pthread_kill(??, ??) at 0xd0508b20
pth_signal._p_raise(??) at 0xd0507f88
raise.raise(??) at 0xd0137280
_SigBusSegvIotHandler(int,int,__sigcontext*)(??, ??, ??) at 0xd1818f60
pth_signal.pthread_kill(??, ??) at 0xd0508b20
pth_signal._p_raise(??) at 0xd0507f88
raise.raise(??) at 0xd0137280
abort() at 0xd01d5864
std::myabort()() at 0xd071770c
std::terminate()() at 0xd0716c6c
exceptio.std::terminate().terminate()() at 0xd0716b8c
except.__DoThrow() at 0xd0f2b0ac
std::_String_base::_Xran() const(??) at 0xd0f34284
string.std::_String_base::_Xran() const.std::basic_string<char,std::char_traits<char>,std::allocator<char> >::erase(unsigned long,unsigned long)(??, ??, ??) at 0xd0f2db4c
rollLogFiles(void*)(0x30241330) at 0x329aeb34

(dbx) whereis rollLogFiles
mttlogger.rollLogFiles(void*)

 

 

Based on the above the crash is happening around method rollLogFiles from mttlogger library that is a Avaya IC library.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms