SMF Definition Will Not Go Offline Until All tcp_smtp_server Processes Finish (Doc ID 2204468.1)

Last updated on NOVEMBER 17, 2016

Applies to:

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

Symptoms

The Oracle-provided example SMF definition results in SMF thinking it should manage/monitor all the descendant processes of the processes it starts.
This is contrary to the Messaging Server design of having watcher managing watching and restarting things, as appropriate.
It results in the SMF service refusing to go completely "offline" until all the tcp_smtp_server processes have exited.
That means "svcadm restart messaging_server" is likely to fail because SMF times out waiting for the tcp_smtp_server children of the old dispatcher process.

There must be some way for the SMF definition to result in behavior more in line with the Messaging Server watcher design.
SMF should watch watcher and pretty much nothing else.

We would expect that when doing "svcadm restart messaging_server", it should restart the service nearly instantly.

Instead of "svcadm restart messaging_server" we have to perform the following steps:

 - svcadm disable messaging_server
 - wait for a while, doing "ps -ef|grep tcp_smtp_server"
 - eventually get tired of waiting and pkill -9 tcp_smtp_server
 - svcadm enable messaging_server

This changes the restart action on an MTA and/or MMP system from something which should be almost 0 impact -- the server should restart and begin taking connections again almost instantly; there should be no need to disable monitoring because the SMTP and IMAP ports should stop listening and begin listening again before anything could notice -- to an outage lasting several minutes.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms