Last updated on AUGUST 21, 2014
Applies to:Oracle Communications Messaging Server - Version 7.0.0 to 7.0.4 [Release 7.0.0]
Information in this document applies to any platform.
Messaging Server 7u4-23.01(184.108.40.206.0) 64bit (built Aug 10 2011)
The imapd daemon is crashing frequently but auto-restarted successfully by watcher.
Using dbx on the original core, we see the crashing thread looked like:
current thread: t@17289
 __lwp_kill(0x0, 0x6, 0x0, 0x0, 0x0, 0x5), at 0xffffffff7b1dbb98
 Abort(0xffffffff1d613680, 0x22d8, 0x17998c, 0x0, 0xffffffff7b33e000, 0x2000), at 0xffffffff7b1c4714
 thr_panic(0xffffffff7b23b068, 0x73, 0x1798b4, 0xffffffff7b1c702c, 0x3a, 0xa), at 0xffffffff7b1c4818
 _ceil_prio_inherit(0xef, 0xffffffff7bb0e200, 0x1706f0, 0xffffffff7b1cd8c4, 0xffffffff7b33e000, 0x0), at 0xffffffff7b1cd964
 mutex_lock_internal(0x114401578, 0x0, 0x0, 0xffffffff7bb0e200, 0xad, 0x1), at 0xffffffff7b1cfb88
=> AsyncAction_Cleanup(p = 0x125f4e070, nWhy = 1), line 2604 in "ASock.c"
 GDisp_Exception(me = 0x1140a05c8, nException = 1), line 2896 in "GDisp.c"
 GDisp_MultiDelete(pgdList = 0xffffffff1d613cf0, ngd = 4U), line 2395 in "GDisp.c"
 shut_down(ctx = 0x111c7c310), line 2599 in "imapd.cpp"
 GDispCx_Dispatch(me = 0x100c90028, pgd = 0x112dedac8, pwtCallback = 0x10c6589a8), line 1541 in "GDisp.c"
 GDispCx_InternalWork(p = 0x10c6589a8), line 1707 in "GDisp.c"
We crash because we are trying to acquire a mutex using a structure which has been freed and because of umem debug, it is overwritten such that it must fail.
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