2004-10-10 11:40:15 java.util.jar.attributes read warning: duplicate name in manifest: class-path2004-10-10 11:40:16 java.util.jar.attributes read warning: Duplicate Name in MANIFEST: CLASS-PATH2004-10-10 11:40:16 java.util.jar.attributes read warning: duplicate name in manifest: Class-path2004-10-10 11:40:16 java.util.jar.attributes read warning : Duplicate name in manifest: class-path2004-10-10 11:40:16 java.util.jar.attributes read warning: duplicate name in manifest: Class-path2004-10-10 11:40:16 java.util.jar .Attributes read warning: duplicate name in manifest: class-path2004-10-10 11:40:16 java.util.jar.attributes read warning: duplicate name in manifest: class-path2004-10-10 11:40:16 java .util.jar.attributes read warning: Duplicate name in manifest: class-path2004-10-10 11:40:16 java.util.jar.attributes read warning: duplicate name in manifest: Class-Path2004-10-10 11: 40:16 java.util.jar.attributes read warning: Duplicate name in manifest: class-path2004-10-10 11:40:16 java.util.jar.attributes read warning: duplicate name in manifest: Class-Pat H2004-10-10 11:40:16 java.util.jar.attributes Read is always constantly reporting this prompt, resulting in starting very slow. What is the reason? Preliminary analysis is as follows:
It seems that if some JAR packets are included in the lib directory of the publishing application, these JAR packages are put in the ClassPath in Server, which is started at the same time, and will display such errors.
result:
In the global classpath set at startup, I went out of the JAR package, and I didn't have an error.
