My Oracle Support Banner

Using DTrace To Analyze Mshttpd Error Reading From IMAP Server (Doc ID 1348074.1)

Last updated on APRIL 15, 2020

Applies to:

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


Starting in Messaging Server 6.3, the webmail server (the mshttpd process)  no longer accesses the message store directly.  It is now an IMAP client.  Thus mshttpd no longer needs to run on the backend server.  It now can be run on the frontend server along with the MMP.  When it has problems communicating with the IMAP server, the Webmail, UWC, or Convergence user will see pop-up errors which basically repeat the status given by mshttpd.  And in the http log file, you will see messages like:

In a large production environment, it can be difficult to know which users are effected, which backend IMAP server is involved, or whether the problem is effecting all users or all backends or only one or a few.

This DTrace script gathers more context around the "Error reading from IMAP server" error from the mshttpd process.

Troubleshooting Steps

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
Troubleshooting Steps
 The mshttpd-imap-errors.d DTrace script
 Sample output
 When to use this script
 Fix for bug 19555861 in

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