org.quartz.threadPool.threadCount

[PRana]

Hi All,

This is a two part question. The following article suggests that maximum value for org.quartz.threadPool.threadCount can be set to 20. 

https://forums.saviynt.com/t5/general-discussions/provisioning-wsretry-thread-count/m-p/2817#M955

1) In our environment, externalconfig.properties file has the org.quartz.threadPool.threadCount=10. Does that override the setting in ${tomcathome}/webapps/ECM/WEB-INF/classes/quartz.properties?

2) Is there any downside to increasing org.quartz.threadPool.threadCount to 20? Why would it not be 20 to begin with?

We have run into the issue a few times where schemauserjob is importing large number of users and evaluation of technical rules can take hours. We have sav.rulerunjobcount=8 and org.quartz.threadPool.threadCount=10. This prevents other jobs from executing so considering the increase of org.quartz.threadPool.threadCount to 20. 

Any thoughts and suggestions are welcome.

Thanks

[rushikeshvartak]

• As you are on v23.8 , change only in externalconfig.properties which will take precedence
• if you increase thread count then no. of pods/ resources /servers should be enough to perform action , by default auto scaling is enabled in saviynt based on customer saviynt license 

[PRana]

I was told by Saviynt team that 10 per node/pod is by default and it is the maximum per node/pod. The maximum thread count of 20 can be reached by having two nodes/pods running.