XCON: MTA Server Work Queue Increases Perfmon UnrealisticallyLast reviewed: April 9, 1997Article ID: Q157068 |
The information in this article applies to:
SYMPTOMSAfter restarting the Microsoft Exchange message transfer agent (MTA), and viewing the Performance Monitor object (MSExchangeMTA, Work Queue Length), the value for this counter continues to increase at an unrealistic rate, and does not accurately reflect the number of work queue items on the work queue.
CAUSEDuring recovery (a process initiated shortly after an MTA restart when it checks and rebuilds the various routing queues), the MTA could loop on an object.
WORKAROUNDThere is no workaround available.
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange version 4.0. This problem was corrected in the latest Microsoft Exchange 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K MORE INFORMATIONRecovery is the process of rebuilding the MTA's queues. After recovery completes, fanout begins. Fanout is the process of placing objects onto the various queues. Enabling medium level logging on "MSExchangeMTA, X.400 Service" allows a log of useful association and send (271)\receive (272) events to be generated. Examining 271 and 272 events can confirm that the MTA has completed recovery and started fanout and delivery of mail. A formula for calculating the approximate number of messages currently awaiting processing by the MTA is:
<the number of *.dat files in \MTADATA>/2Fanout can be expected after the Work Queue Length approaches this calculated estimate. (The perfmon counter may exceed this estimate by 15 to 20 percent before fanout is observed.) If all of these conditions are met, it is likely you are experiencing this problem and should obtain the fix noted in the "Status" section of this article:
|
Keywords : kbbug4.00 kbfix4.00.sp4 kbusage XADM kbbug4.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |