CA 7 Web Client Started Task High CPU Consumption

Products

• CA 7 Workload Automation

Issue/Introduction

The CA 7 Web Client task consumes extremely high CPU in the first 20-25 minutes after the start-up, as it scans all the directories regardless of their relevance.

Cause

Insufficient free space available after evicting expired cache entries messages.

Resolution

Modify the context.xml file and recycle CA 7 Web Client

1. Open the /install/apache-tomcat-9.0.56/conf  subdirectory of the Web Client USS filesystem (e.g. /CA/ca7webclient/install/apache-tomcat-9.0.56/conf) using ISPF 3.17

2. Enter 'EA' next to to the context.xml file

3. PF8 to the bottom and you should see:
        <!-- Uncomment this to disable session persistence across Tomcat restarts -->
        <!--                                                                         
        <Manager pathname="" />                                                      
        -->                                                                          
    </Context>   
   
   If you don't, cancel your edit session and contact Broadcom support with all the info.  If you do see the above then:

4. Insert the Resources line and JarScanner lines as shown below.  Note it is very important they are after the two bolded line otherwise they will be considered a comment.
        <!-- Uncomment this to disable session persistence across Tomcat restarts -->
        <!--                                                                         
        <Manager pathname="" />                                                      
        -->    
        <Resources cacheMaxSize="100000" cachingAllowed="true"/> 
        <JarScanner scanClassPath="false"/>                             
    </Context>      

5. Recycle Web Client.