CA Spectrum OneClick client has performance issues and the following shows in the tomcat log: waitForReadTasks timed out

book

Article ID: 6384

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

The OneClick client is slow and may show the following symptoms:

  • Frequent disconnect/reconnects (red border)
  • Topology views hang when initializing
  • List views take a long time to populate
  • Searches take a long time to produce results.

When reviewing the OneClick Tomcat log, the "waitForReadTasks timed out" message is seen:

<MONTH> <DAY>, <YEAR> <Hr>:<Min>:<Sec> (http-bio-443-exec-2) (MODELREPO) - waitForReadTasks timed out

 

Cause

The problem is due to a bottleneck with the amount of information being processed in the model repository.

Environment

Spectrum 10.4.x / 20.x

Resolution

Change the ModelRepository reads from 500 to 5000 in the file:

$SPECROOT/tomcat/webapps/spectrum/WEB-INF/web.xml


So change the following:

<context-param xmlns="">

<param-name>com.aprisma.topo.ModelRepository.ThrottledModelReadCount</param-name>

<param-value>500</param-value>

<description>

This parameter defines the maximum number of models the Model Repository will read in a single request to a SpectroSERVER.

</description>

</context-param>

To this:

<context-param xmlns="">

<param-name>com.aprisma.topo.ModelRepository.ThrottledModelReadCount</param-name>

<param-value>5000</param-value>

<description>

This parameter defines the maximum number of models the Model Repository will read in a single request to a SpectroSERVER.

</description>

</context-param>

 

Then Stop and restart tomcat for the change to take effect.

Additional Information

The com.aprisma.topo.ModelRepository.ThrottledModelReadCount parameter in the web.xml has been increased to 5000 by default in Spectrum 10.03.00.

If you are still seeing this error, increase the value to 7500 and cycle tomcat