How to increase processing threads of NAC?


Article ID: 197777


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


In some large environments, where the default available processing threads of 10 are not sufficient for NAC it is often recommended to configure the same. This document illustrate how to increase the processing threads of NAC.


Why default available processing threads at NAC are not adequate?

It can be because of below two reasons.

  1. Queue is very long, new tasks getting registered but executed slowly or not at all
  2. Queue is relatively short, but all threads (10) which are processing tasks are stuck on some type of task.




Note: Please consult technical support in case of doubt before making the below change. When contacting technical support please collect NAC thread statistics (How to collect NAC thread statistics?) and share the same with them, so they can suggest post review if the mentioned recommendation is a viable change to make.


Release : 6.6, 6.7



Steps to configure processing threads of NAC

1) Locate file wrapperContext.xml and create a backup of same

File Location: NAC_INSTALL_DIR\webapps\datamanagement\WEB-INF\wrapperContext.xml

2) Open the file in edit mode and locate below section

    <bean name="mainScheduledThreadPoolExecutor" class="java.util.concurrent.ScheduledThreadPoolExecutor">
        <constructor-arg index="0" type="int" value="10"/> 
        <property name="maximumPoolSize" value="200" />

3) Modify the <constructor-arg index="0" type="int" value="50"/>. The section post modification will be as below

 <bean name="mainScheduledThreadPoolExecutor" class="java.util.concurrent.ScheduledThreadPoolExecutor">
        <constructor-arg index="0" type="int" value="50"/>
        <property name="maximumPoolSize" value="200" />



  1. For NAC the Release Automation product will create only 1 CentralScheduledTaskExecutor with 10 thread processing NAC tasks
  2. The maximumPoolSize property is ignored
  3. With above change we are making CentralScheduledTaskExecutor to be created with 50 thread.