Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Exchange and process queue length.

I'm running Exchange 2003. getting NetPerMon Event Log: Component Process Queue Length on Application Exchange Server 2003 on Node is Critical What does this mean?

Find more posts tagged with

Accepted answers

All comments

RogerWong

Sorry for the confusion. The name of this component should actually be "processor queue length". The processor queue length is the number of threads currently waiting to be processed by the CPU. According to Microsoft's article below, this value should not exceed 2 processes for any system. A consistently high value is a sign of CPU congestion.

Microsoft Article: Win32_PerfRawData_PerfOS_System Class

ProcessorQueueLength

Data type: uint32
Access type: Read-only
Qualifiers: DisplayName("Processor Queue Length"), CounterType(65536), DefaultScale(1), PerfDetail(400)

Number of threads in the processor queue. There is a single queue for processor time even on computers with multiple processors. Unlike the disk counters, this property counts ready threads only, not threads that are running. A sustained processor queue of greater than two threads generally indicates processor congestion. This property displays the last observed value only; it is not an average.

denniscurtains

My advice. Drop Exchange 2003. We use it at our office and we have nothing but trouble with it.