https://bz.apache.org/bugzilla/show_bug.cgi?id=60753
Bug ID: 60753
Summary: After upgrade from 8.0.39 to 8.0.41,
StandardJarScanner complains about missing jars
Product: Tomcat 8
Version: 8.0.41
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: listcraig...@yahoo.com
Target Milestone: ----
After an upgrade from Tomcat 8.0.39 to 8.0.41, an application no longer starts.
In the catalina log file, there are many exceptions of the type:
WARNING [localhost-startStop-1] org.apache.tomcat.util.
scan.StandardJarScanner.scan Failed to scan
[file:/usr/share/java/tomcat8/javax.
annotation-api.jar] from classloader hierarchy
java.io.FileNotFoundException:
/usr/share/java/tomcat8/javax.annotation-api.jar
(No such file or directory)
The files complained about belong to jaxws-ri. Even after copying all 23 jars
from the jaxws-ri 2.2.10 lib directory to the Tomcat lib directory (per the
documentation of jaxws-ri), exceptions for additional jars apparently
referenced by jaxws-ri (and some with very specific build versions) persist:
jaxb-core-2.2.10-b140802.1033.jar
jaxb-api-2.2.12-b140109.1041.jar
istack-commons-runtime-2.19.jar
txw2-2.2.10-b140802.1033.jar
hk2-core.jar
class-model.jar
config.jar
auto-depends.jar
javax.inject.jar
hk2-api.jar
osgi-resource-locator.jar
tiger-types.jar
bean-validator.jar
jtype.jar
It looks like the jar scanner has suddenly become very picky about the presence
of all these files, even though the application works perfectly fine without
them. Please restore the more permissive operation of the scanner from 8.0.39.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
