Work scheduler requesting 1min/50max threads, but not available. 

Document ID : KB000127264
Last Modified Date : 19/02/2019
Show Technical Document Details
Introduction:
we see the below warnings in spectrum control panel.

an 04 14:06:36 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Jan 04 14:06:36 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Jan 04 14:06:36 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Jan 04 14:06:36 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Jan 04 14:06:36 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Jan 04 14:06:36 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Jan 04 14:08:18 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Jan 04 14:08:18 WARNING at CsWorkSched.cc(173): Low thread resources detected. Work scheduler requesting 1min/50max threads, but not available. 
Environment:
Spectrum Version 10.2.2
 
Instructions:
These are Native threads which accept requests from OneClick and other clients.
They are put in the work queue and from there Moot is processing each request.

To fix this:
increase the work threads in VNM-> information tab -> Thread -> work thread 
We need to  increase the respective thread Max value by 10/20/50 basing on the environment. 
A. Silna in SE has recommended to try the solution in the following which customer has enabled and is testing. 1. Change the value from 500 to 5000 of com.aprisma.topo.ModelRepository.ThrottledModelReadCount property in /tomcat/webapps/spectrum/WEB-INF/web.xml file. Stop and restart tomcat for the change to take effect. If this is not showing any improvement , then please collect below logs 1. Stop tomcat ,Take a backup of custom folder in SPECROOT and then start tomcat. Custom folder will be again created , but stays empty. 2. Try to reproduce the issue again and collect tomcat logs. Please turn on debug "Global Collection Topology" 3. If this is also not giving any clue ,then we may need thread dumps. B. I have also requested to install bmp2 for 10.2.3, where we see the resolved issues on discovery below. While the problem is seen after a discovery, the libadisc.dll may not be the cause but there are updates to many dlls included on BMP2 that resolve a host of known issues. Snmp engine ID discovery (DE334682, 00897842) SNMPv3 isssue while discovering infoblox servers. (DE340061, 00935000 ) Symptom: SpectroSERVER got crashed while discovering connections on Alcatel devices. Resolution: Discover connection will be successful for Alcatel devices. (DE355138, 00996619) Symptom: SpectroSERVER crash during LLDP connection discovery. Resolution: SpectroSERVER will not be crashed during LLDP connection discovery. (DE359148, 01064523)