Topic Last Modified: 2010-02-16

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers running Exchange 2010. For this Operations Manager rule, data is collected by using the performance counter specified in the Details table.

To review the value of the performance counter that generated this alert, in Operations Manager, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Object Name

MSExchangeTransport Queues

Counter Name

Submission Queue Length

Instance Name

_Total

Sample Interval

60

Server Role

Ex14. Edge Transport

Critical Error Threshold

250

Rule Path

Microsoft Exchange Server/Exchange 2010/Edge Transport/Transport Queues

Rule Name

Submission Queue Length - sustained for 5 minutes - Red(>250) - Edge Transport.

Explanation

The Submission Queue Length performance counter measures the number of messages currently in the submission queue. Messages in this queue are in a retry state because an issue prevented their submission to the categorizer. If the issue is transient, a subsequent attempt to submit the message may be successful.

This alert indicates that the submission queue length has been greater than 250 for five minutes. A sustained high Submission Queue Length value may indicate that an excessive amount of inbound messages have over loaded the categorizer. It may also indicate that there is an issue with message categorization. Message resubmission sends undelivered messages back to the Submission queue to be reprocessed by the categorizer.

A sustained high Submission Queue Length may be caused by one or more of the following:

  • The server is being over-utilized and does not have enough resources to satisfy all current requests. This situation may occur if there are more messages being submitted for transport then the server can handle. Similarly, it may also occur if many messages are being resubmitted for categorization.

  • There is a problem with a custom agent or rule, or a third-party agent or rule.

For information about the submission queue, see Understanding Transport Queues.

User Action

To resolve this alert, try one or more of the following:

  • If you believe that the server is being over-utilized, determine what is causing the extra load on the server and try to minimize the load.

  • If you believe that there are too many messages being received by the server, try to remove the messages from the submission queue. For example, it might be necessary to remove the server from the network to allow messages to drain from the submission queue. If you can determine that the messages in the submission queue are all inbound from an external source, consider disconnecting the server from the external network. This action will give the server time to process all the messages currently in the message queues.

  • To determine if an agent or message rule is causing the issue, disable all Transport agents and rules and see if the queue clears. If this resolves the issue, enable the Transport agents or rules one at a time to determine the specific object causing the problem.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.