'Imsconnutil -k' Should Interrupt IMAP SEARCH (Doc ID 2469950.1)

Last updated on JUNE 24, 2024

Applies to:

Goal

The following Enhancement Request was fixed in Oracle Communications Messaging Server 8.0.2.2.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 ?

Solution

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