At least one JAR was scanned for TLDs yet contained no TLDs

Products

• CA Service Desk Manager
• CA Service Management - Service Desk Manager

Issue/Introduction

The following appears in the NX_ROOT\pdm_tomcat log after starting Tomcat: 

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.

Is the above a concern?  Will it affect Tomcat logging?

Environment

CA Service Desk Manager 17.3 or higher

Resolution

To see JARs that were scanned that did not contain any TLDs, modify the logging.properties file at NX_ROOT\bopcfg\www\CATALINA_BASE\conf

1) Change the following line

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = INFO

To

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = FINE

2) Uncomment the following line:

org.apache.jasper.compiler.TldLocationsCache.level = FINE

3) Add the following line to the bottom of the logging.properties file:

org.apache.jasper.servlet.TldScanner.level = FINE

4) Then recycle Tomcat with the following commands:

pdm_tomcat_nxd -c STOP

WAIT 20 SECONDS

pdm_tomcat_nxd -c START

5) Once the JARs have been captured they can be added to the catalina.properties file in the same location under:

# List of JAR files that should not be scanned for configuration information

Additional Information

The above is provided to allow administrators the opportunity to examine for jar files that lack TLDs, and should only be done in non-prod environments.  One does not need to be concerned with TLD content for Tomcat logging.

Generally, Tomcat logging can be activated by running through steps in KB Article 438200.  

Information about Java TLD (Tag Library Descriptors) can be found here