I'm upgrading to Apache Tomcat 8.5.15 from 6.0.44. When I start up the web server and deploy my web application, I get lots of warnings from org.apache.tomcat.util.scan.StandardJarScanner.scan with the message
Failed to scan [file:/path/to/apache-tomcat/lib/lib/tomcat-jaspic-api-8.5.15.jar] from class loader hierarchy
java.io.FileNotFoundException: /path/to/apache-tomcat/lib/lib/tomcat-jaspic-api-8.5.15.jar (No such file or directory)
I don't understand why the scanner is looking inside apache-tomcat/lib for another directory named lib, which doesn't exist. My CATALINA_HOME is set to /path/to/apache-tomcat and the common.loader property in catalina.properties is set to the default:
common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar"
I know that the warning can be safely ignored without affecting the web application, and that I can turn off JAR scanning in apache-tomcat/conf/context.xml, but I'd still like to know the reason behind the lib/lib oddness.
