Last updated on DECEMBER 20, 2016
Applies to:Oracle Communications Messaging Server - Version 5.2.0 and later
Information in this document applies to any platform.
Checked for relevance on 01-Nov-2015
On some backend message store systems, the imapd processes begin consuming more memory than usual around peak load time and response time degrades. Restarting imapd clears the problem until the next peak load time.
The increased memory usage is actually a side effect. The primary symptoms would be degraded response time and increased number of threads waiting in the mmap() syscall. See more details in the Cause section below.
Customer recently upgraded from Messaging Server 5.2 to 7.x and did not maintain similar configuration/tuning parameters.
Note that this issue could also be caused by steady usage growth, which might not be noticed as a "change".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms