MaxConcurrentFastMsgsThreadPoolSize and MaxConcurrentSlowMsgsThreadPoolSize

Products

• IT Management Suite

Issue/Introduction

Are these two settings still in use on recent versions?:
MaxConcurrentFastMsgs and MaxConcurrentSlowMsgs

Environment

ITMS 8.x

Resolution

After SMP 7.1 SP2 the following settings were introduced, replacing the two: MaxConcurrentFastMsgs and MaxConcurrentSlowMsgs (those are not longer used and on new SMP 7.1 SP2 installations will not be present the all):
MaxConcurrentFastMsgsThreadPoolSize and  MaxConcurrentSlowMsgsThreadPoolSize

However, MaxConcurrentSlowMsgsThreadPoolSize is not used anymore –slow / large message processing is now defaulted to have 1 thread per queue (one for “slow” and one for “large”).

Regarding changing the values for MaxConcurrentFastMsgsThreadPoolSize as we did with MaxConcurrentFastMsgs, there is not a specific reason that we would like to decrease the values, but it should not bring any troubles at all. If we need to change the value as a way to just to avoid deadlocks while processing NSEs, it’s absolutely fine, either decreasing or increasing.

"Troubleshoot NSE Processing in 8.5 and later" (KB 172741)

Additional Information

"How to troubleshoot NSE processing issues" (KB 205352)
"How to check for excessive NSE files in the EventQueue and be alerted when too high" (KB 232716)