My Oracle Support Banner

Threads in IMAPD Processes Stuck Waiting to Acquire a Lock on the User's Inbox (Doc ID 2780829.1)

Last updated on JUNE 02, 2021

Applies to:

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

Symptoms

Consider a setup with a few users with hundreds of connections, each tying up a thread in IMAPD processes stuck waiting to acquire a lock on the user's INBOX which is locked by a reconstruct command which is taking hours.

If they don't catch them in time, they build up enough to lock up all the threads in all the IMAPD processes.

If they have to restart IMAPD, most of the IMAPD processes will fail to shut down properly because of these threads stuck waiting for these locks. That will cause STORED to be restarted, which will abort the reconstruct and they will need to start them all over.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.