Poison Queue Length - sustained for 5 minutes - Yellow(>1) - Edge Transport
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers that are running Exchange Server 2007. For this Operations Manager rule, data is collected using the performance counter specified in the Details table.
To review the value of the performance counter that generated this alert, do one of the following:
If you are using Microsoft Operations Manager 2005, from the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.
If you are using System Center Operations Manager 2007, 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 |
8.0 (Exchange Server 2007) |
Event Source |
MSExchangeTransport Queues |
Counter Name |
Poison Queue Length |
Instance Name |
_Total |
Sample Interval (in seconds) |
60 |
Server Role |
Ex. Edge Transport |
Warning Threshold |
>1 |
Critical Error Threshold |
>5 |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Edge Transport/Transport |
MOM Rule Name |
Poison Queue Length - sustained for 5 minutes - Yellow(>1) - Edge Transport. |
Explanation
The Poison Queue Length performance counter measures the number of messages currently in the poison queue. Messages in the poison message queue are in a permanently suspended state.
This alert indicates that the Poison Queue Length has been greater than 1 for five minutes.
The poison message queue contains messages that are determined to be potentially harmful to the Microsoft Exchange Server 2007 server after a server failure. The messages may be genuinely harmful in their content and format. Alternatively, they may be the results of a poorly written agent that has caused the Exchange server to fail when it processed the supposedly bad messages.
Messages remain in the poison message queue until they are manually resumed or removed by an administrator. The messages in the poison message queue are never automatically resumed or expired.
User Action
To resolve this alert, resubmit or remove the messages from the poison message queue. You can resubmit the messages that are in the poison message queue by using the Exchange Queue Viewer or by running the Resume-Message cmdlet. You can remove messages from the poison message queue by using Queue Viewer or by running the Remove-Message cmdlet.
Note
You cannot resubmit messages in the poison queue using the Retry-Queue cmdlet with the Resubmit parameter.
For information about Queue Viewer, see Using Queue Viewer to Manage Queues.
For information about the Resume-Message cmdlet, see Resume-Message.
For information about the Remove-Message cmdlet, see Remove-Message.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Microsoft Help and Support Web site.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.