2014-09-04 19:55 GMT+04:00 Martin Knoblauch <knobis...@gmail.com>: > > It seems it happens between 7.0.42 and 7.0.47. I would "bisect", but cannot > find any tarballs between those two releases. >
Those versions have been votes as broken and not released. >> > 2) How can one find out which jars are "problematic" >> >> Not easily. Your best bet would be to write a short app that parsed the >> Manifest of each Jar file in turn. >> >> > Have to think about it. Time you know. But thanks. > a) You may try debugging: https://wiki.apache.org/tomcat/FAQ/Developing#Debugging You could get stack trace and function arguments (such as file name). b) You may use zip archiver (or jar archiver from JDK) to unpack their manifest files and read through them. c) JDK 7u67 source code for java.util.jar.Attributes contains [[[ if ((putValue(name, value) != null) && (!lineContinued)) { PlatformLogger.getLogger("java.util.jar").warning( "Duplicate name in Manifest: " + name + ".\n" + "Ensure that the manifest does not " + "have duplicate entries, and\n" + "that blank lines separate " + "individual sections in both your\n" + "manifest and in the META-INF/MANIFEST.MF " + "entry in the jar file."); } ]]] None of Tomcat jars have "Depends-On" entry in their manifests. Such an entry is surely not the first one in the file (the first one should be Manifest-Version), so it is unlikely that the manifest file is being read twice. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
