BUG: No Event When MSMQ Reaches Paged Pool Limit (264936)
The information in this article applies to:
- Microsoft Message Queuing 2.0
This article was previously published under Q264936 SYMPTOMSWhen Message Queuing (also known as MSMQ) detects 80 percent usage of the system paged pool, all creation of new messages is suspended. In MSMQ 1.0, during periodic checkups of the memory status by the MSMQ service, the following messages are written to the event log when the memory status changes:
Event QM_LOW_MEMORY (2070): Computer is low on memory. MSMQ Service is switching to "low memory" mode of operation.
Event QM_ENOUGH_MEMORY(2071): Computer has enough free memory. MSMQ Service is returning to normal mode of operation.
With MSMQ 2.0 on Microsoft Windows 2000, there are no periodic checkups, and no event to indicate this error. The MSMQ 2.0 service memory driver checks the available space at each allocation of memory, and adjusts the mode accordingly.
RESOLUTION
When the MSMQ service moves into the low memory operational state, no new messages are accepted or created by the service. If this behavior occurs, use the Performance Monitor (perfmon) tool to monitor the system paged pool usage, and determine if it is the usage level that is causing this behavior.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. REFERENCES
See the MSMQ Administrator's help for information on administration of the MSMQ service.
| Modification Type: | Major | Last Reviewed: | 9/18/2003 |
|---|
| Keywords: | kbBug KB264936 |
|---|
|