Epoxy Store Out Queue Length (IMAP) beyond threshold
Topic Last Modified: 2006-02-13
The Microsoft® Exchange Server Analyzer Tool includes a performance data collection engine that is used to query performance counter objects on computers that are running Exchange 2000 Server or Exchange Server 2003. The performance data collection engine collects data from the Store Out Queue Length (IMAP) performance counter of the Epoxy performance object to analyze performance data.
The Store Out Queue Length (IMAP) performance counter indicates the number of messages in the queue that contain IMAP4 messages sent by the Store.exe process to the Inetinfo.exe process. The queue should be under 50 at all times. The Exchange Server Analyzer retrieves a sample from this counter every 5 seconds for a five minute period. If the Exchange Server Analyzer determines that the Store Out Queue Length (IMAP) counter has exceeded the peak value of 50 during the sample time slice, the Exchange Server Analyzer displays an error.
Epoxy (ExIPC) is a shared memory mechanism that enables the processes of the Microsoft Internet Information Services (IIS) (Inetinfo.exe) and Microsoft Exchange Information Store services (Store.exe) to quickly shuttle data back and forth. This allows for bi-directional, interprocess communication between the Inetinfo.exe process and the Store.exe process.
|Inetinfo.exe accepts requests from Internet protocols such as WebDAV, IMAP4, NNTP, POP3, and SMTP.|
This memory is also used by DSAccess, the Exchange component that caches Active Directory® information.
This error indicates that there are performance issues in the Inetinfo.exe process, or in resources that the Inetinfo.exe process depends on, that are causing this queue to grow. This may cause server response time to increase. Therefore, users will experience delays in response from the server.
To resolve this issue, use the resources referenced in the "More Information" section to identify the performance bottleneck with Inetinfo.exe or related resources. This bottleneck may be related to poor disk performance or high CPU utilization.
For more information about identifying increasing queues in Epoxy, see "Identifying Rising Queues in Epoxy" in Troubleshooting Microsoft Exchange Server Performance (http://go.microsoft.com/fwlink/?LinkId=47588).
For more information about processor bottlenecks, see Processor Bottleneck.
For more information about disk bottlenecks, see Disk Bottleneck Detected.
For more information about troubleshooting store performance, see Microsoft Knowledge Base article 257725, "XADM: How to Collect Diagnostic Data for Information Store Troubleshooting" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=257725).
For more information about Exchange Server performance, see the Performance and Scalability Guide for Exchange Server 2003 (http://go.microsoft.com/fwlink/?LinkId=47576).
For more information about troubleshooting Exchange Server performance issues, see Troubleshooting Microsoft Exchange Server Performance (http://go.microsoft.com/fwlink/?LinkId=47588).