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

Products

• DX NetOps
• 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

Environment

Release: All Supported Releases

Component: SPCOCK - OneClick

Cause

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

Resolution

Change the ModelRepository reads from 5000 to 7500 in the $SPECROOT/tomcat/webapps/spectrum/WEB-INF/web.xml file

- Log into the OneClick system as the user that owns the Spectrum installation

- Make a backup of the current $SPECROOT/tomcat/webapps/spectrum/WEB-INF/web.xml file

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

- Look for the following:

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

- Change the value from 5000 to 7500:

<context-param xmlns="">

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

<param-value>7500</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>

- Save the change

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

Additional Information

If the messages still appear, change the value to 10000.