--- Comment #15 from Mauro Molinari <> ---
I think I also encountered this problem after deploying in Tomcat 8.5.5 a
webapp previously run in Tomcat 8.0.14.
I have a lot of WARNING: file not found for JARs mentioned in useless
Class-Path entries in JARs deployed in WEB-INF/lib, like jaxb-impl-2.1.13.jar
(which mentions "jaxb-api.jar activation.jar jsr173_1.0_api.jar
jaxb1-impl.jar") or 
xalan-2.7.2.jar (which mentions "xercesImpl.jar xml-apis.jar serializer.jar").

Fact is that some of those JARs (at least those I really need) are deployed
with different names (with a version specifier, for instance), as resolved by
tools like Gradle or Maven).

So my Tomcat log on startup is now full of these warnings that look like errors
a lot (they're complete with stack traces).

Maybe lowering the log output to debug level and/or remove stack traces could
also be much less intrusive than the current bevahiour?

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to