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

Article Id: 127264
Status: Published
Updated On: 15-06-2020 18:39
Products:
CA Spectrum , CA Spectrum , CA Spectrum , CA Spectrum
Issue/Introduction:

The following warning messages are repeatedly generated in the Spectrum Control Panel (SCP)/ VNM.OUT.

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: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. 

Cause:

These are Native threads which accept requests from OneClick and other clients. They are placed in the work queue and from there, Moot is processing each request.

Environment:

Spectrum 10.2.x

Resolution:

Increase the work threads under VNM-> information tab -> SpectroSERVER Control -> Thread Information -> work thread 

We need to  increase the respective thread Max value by 10/20/50 based on the environment. 

Change the value from 500 to 5000 of com.aprisma.topo.ModelRepository.ThrottledModelReadCount property in the $SPECROOT/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 the following logs and open a support ticket:

1. Stop tomcat ,Take a backup of custom folder in $SPECROOT and then start tomcat. Custom folder will be created again, 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.

While the problem is seen after a discovery, the libadisc.dll may not be the cause but there are updates to many dlls included in Spectrum 10.2.3 BMP2 that resolve a host of known issues, such as:

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)