Last updated on JUNE 29, 2017
Applies to:Oracle Communications Messaging Server - Version 6.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Nov-2012***
After a mass mailing or spam attack or other event causing thousands of messages to be suddenly enqueued to a specific channel, it seems as if the backlog is processed aggressively for a short time and then very slowly after that.
Doing "ps -ef | grep ims_master" shows only a few processes. If you restart job_controller, there will be many ims_master processes for a short time, but then it goes back to only 1 or a few.
And "imsimta qm summary" shows many messages in the queue.
And "imsimta qm dir <channel>" shows many of them are ZZ* messages -- indicating they have not yet been tried.
As long as there is a steady flow of new messages being enqueued to the channel in question, job_controller keeps sufficient worker processes running and the queue will decrease.
But when the rate of incoming mail to that channel drops (or stops completely) the number of worker processes drops and progress slows significantly.
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