Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-6388:In centrifydc.log, what does 'Pool size' and 'busy size' mean?

Authentication Service ,   Mac & PC Management Service ,  

12 April,16 at 10:59 AM

Applies to:
All Centrify DirectControl version on all platforms

When Centrify debug is turned on, the following log line is commonly observed:

DEBUG <main> util.threadpool Pool size A/B, busy size X/Y

What is the meaning of this line?


A=the number of threads currenly allocated but idle
B=the number of threads adclient allocated when starting up.  This is configurable by 'adclient.clients.threads' and the default value is 4
X=the number of threads currently busy doing some work
Y=the maximum number of threads adclient can allocate and use.  This is configurable by 'adclient.clients.threads.max' and the default value is 20

Adclient maintains a thread pool of threads available with no more than the number set by 'adclient.clients.threads'.  When a new request comes in, adclient gets a thread from the idle thread pool (A) if one is available.  If there is no thread available in idle thread pool, adclient would allocate a new thread until the total thread reaches the max thread (A+X=Y)

When a busy thread (Y) finished its job, it returned thread to the idle thread pool until the idle thread pool reaches the startup thread number (B), at that time the freed thread will be returned to the system.

Both configuration parameters can be set either in /etc/centrifydc/centrifydc.conf or through the Centrify Group Policy extensions.


Related Articles

No related Articles