CA 7 Web Client takes a long time to start up
Article ID: 379637
Updated On:
Products
Issue/Introduction
When CA7 Web Client STC is started it needs around 45 minutes to complete the start-up process and is using a lot of CPU (50%-70%).
There are also Security violations. For example:
01.02.03 STC12345 ICH408I USER(user ) GROUP(group ) NAME(name) 100
100 /directory/servers
100 CL(class) FID(fid…)
100 INSUFFICIENT AUTHORITY TO OPENDIR
100 ACCESS INTENT(R--) ACCESS ALLOWED(OTHER ---)
100 EFFECTIVE UID(uid) EFFECTIVE GID(gid)
01.02.03 STC12345 ICH408I USER(user ) GROUP(group ) NAME(name) 100
100 /directory/preauth
100 CL(class) FID(fid…)
100 INSUFFICIENT AUTHORITY TO OPENDIR
100 ACCESS INTENT(R--) ACCESS ALLOWED(OTHER ---)
100 EFFECTIVE UID(uid) EFFECTIVE GID(gid)
And many more.
One of the messages generated is:
PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Environment
CA 7 workload automation Web Client 12.1.1.202112101949
Cause
Missing <JarScanner scanClassPath="false"/> line in ../conf/context.xml
Resolution
Add:
<JarScanner scanClassPath="false"/>
to ../conf/context.xml -
Once this line is added to the context.xml CA7 Web client starts immediately without delays.
Additional Information
If scanClassPath is not coded then the default (true) is used so the full web application classpath, including the shared and common classloaders and the system classpath (but not the bootstrap classpath) will be scanned for Jar files in addition to the web application
Feedback
