My Oracle Support Banner

Where Does The MTA Keep The Message Data Until It Knows Where To Enqueue? (Doc ID 1945530.1)

Last updated on MARCH 07, 2019

Applies to:

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

Goal

It is convenient to think the tcp_smtp_server process writes the message directly to the destination channel queue as it receives the data, but that gross over-simplification can lead to under configuration of memory/swap on MTA systems -- or over commitment via the MAX_PROCS and MAX_CONNS dispatcher config options -- which can lead to unexpected system memory/swap shortage and processes randomly crashing.

So if it does not immediately write the data directly to the destination channel queue directory, where does the MTA store the message data as it is receiving it?

What limits can prevent the MTA from consuming all system memory holding such data -- causing "unix: WARNING: /tmp: File system full, swap space limit exceeded" messages?

Solution

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
Goal
Solution
 Process heap and /tmp
 You cannot see the files in /tmp
 What limits are available?
 Reducing MAX_PROCS may cause delays during peak load - and that's ok
 Add swap or change MTA tmpdir
References


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