Smart Plug-in for WebLogic Server Reference Guide

1-18

Chapter 1

Metric B012_ExQueWaitCnt

Monitor Template Name WLSSPI_0012

Metric Name Execute Queue Wait Count

Metric Type Alarming, Graphing

Description The number of client requests waiting to be serviced

WebLogic 6.0/6.1 or Both Both

Severity: Condition Minor: WLSSPI-0012.1, threshold 10

Collection Interval 15m

Message Text WLSSPI-0012.1: # of requests waiting to be serviced (<$VALUE>) too high

(>=<$THRESHOLD>)

Instruction Text The number of client requests waiting to be serviced has exceeded a threshold

value.

Probable cause: The rate of incoming requests has exceeded the number of

threads available to perform the work.

Potential impact: Degradation in performance from a client perspective.

Suggested action: Although client requests are waiting for an execute thread to

be allocated, it is important to note that adding more threads does not

necessarily imply that you can process more work. Even if you add more

threads, you are still limited by the power of your processor. You can degrade

performance by increasing this value unnecessarily. Because threads are

resources that consume memory, a very high execute thread count causes more

memory to be used and increases context switching. This degrades your

performance.

If this condition persists, you may need to upgrade your processor power.

Another solution is to simply add resources. If your WebLogic server is

configured in a cluster, then to increase the load handling capabilities you can

add another WebLogic server to the cluster. Given a well-designed application,

adding additional servers should provide linear scalability.

For information on tuning the execute thread pool, see the 'Performance and

Tuning' documentation for your WebLogic Server version available through

http://e-docs.bea.com/.

Area Performance