Running Policy Server, the statistics shows "Current Thread" value equal to "Max Thread" permanently

Document ID : KB000012507
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

Running Policy Server, this ones shows in its stats the "Current Threads" has
always the same value as "Max Threads", and I would like to know why.

Environment:
Policy Server 12.51CR08 on RedHat 6 64bit;Policy Store on Sun Directory Server 11.1.1.3.0;
Answer:

Since 12.5, the Policy Server creates all of the worker threads at start up time
itself and it no longer closes these worker threads even after being idle.

That's the reason for having "Current Thread" equal to "Max Thread".

If you need to evaluate if you run too many threads or too few, you might
evaluate the load of the defined threads by monitoring those fields :

To illustrate :


   Msgs=25125 Waits=25014 Misses=3401


  Msgs=25125 - This is the total number of requests that have been received.

  Waits=25014 - This is the number of times that a thread went to get a
  request from the queue to process, but had to wait for one to arrive.

  Misses=3401 - This is the number of times that a thread went to get a
  request from the queue to process, had to wait for one to arrive,
  but none came in before the thread went back to sleep.

So said, a high value of "Misses" means that you have probably defined too many
threads. With "Msgs" and "Waits" values close to be the same, combined with a low "Misses"
will mean that the Policy Server runs an appropriate amount of threads.

A large "Msgs" value coupled with a low "Waits" value and a low "Misses" value would imply
that you may need to increase the number of worker threads.