Attempting to load its LogManager class in mantis, the SunOne appserver gets an ExceptionInInitializerError and exits. Although this looks similar to the problem reported in bugid 4761452, the root cause is different (and the fix for that bug doesn't solve this problem).

The issue is an interaction between java.util.jar.Attributes and the LogManager. When the Attributes class processes a multi-line Class-path, it calls putValue() multiple times with the same name (Class-path). This triggers a call to to logger to log that there is a duplicate name in the manifest file. [It seems like that's the real error here; there are not duplicate names in the manifest -- the putValue shouldn't be called for every line, just for every name.]

When the jar file being loaded contains the class defined by the java.util.logging.manager property, then the LogManager class cannot complete its initialization, and the end result is an ExceptionInInitializerError [with the fix for 4761452, the end result is a ClassNotFoundException].