Why Did watcher Not Notice imapd Crash on Shutdown? (Doc ID 1189614.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

Oracle Communications Messaging Server - Version 6.0 and later
Information in this document applies to any platform.

Symptoms

IMAP response time degrades, imapd threads build up, pstack shows threads waiting for locks in the DB, processes like mboxutil or reconstruct hang, and imcheck -s shows the process holding the lock iss a PID that no longer exists.

You might also see DB transaction log files accumulating.

If autorestart is enabled, once all the imapd threads are hung, msprobe would detect IMAP being unresponsive and call for restart of all the store processes, that would clear the problem, but is a non-optimal way to clear it.

Changes

The customer had recently restarted only the imapd processes rather than a full restart of Messaging Server.

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