'Imsconnutil -k' Should Interrupt IMAP SEARCH
(Doc ID 2469950.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
The following Enhancement Request was fixed in Oracle Communications Messaging Server 220.127.116.11.20180519:
ER bug 27910992 - Halt a classic search between a scan of any two messages upon shutdown of imapd
There appears to be an issue with 'imsconnutil -k' for IMAP connections which are equally busy in a long SEARCH.
A sample user being observed having 300 connections, all busy in IMAP SEARCH, can cause a severe impact on the back-end. So an attempt to disconnect the user using 'imsconnutil -k -u <userid>' command will result in 'imsconnutil -c' command not showing that user any more.
However, the CPU problem persist for several minutes.
Some time later, log entries show the search requests for those connections ending.
The behavior where 'imsconnutil -k' causes 'imsconnutil -c' to not show those connections when they still existed seem like a bug.
Is it currently possible for 'imsconnutil -k' to interrupt and disconnect those in-progress search connections, just like Messaging Server shut down does ?
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