-
Bug
-
Resolution: Future Project
-
P4
-
1.4.2
-
None
-
x86
-
windows_2000
If logging calls are made early in the initialization sequence before
the LogManager class is loadable this may cause an ExceptionInInitializerError.
Normally the LogManager is part of rt.jar and can always be loaded safely.
However, if the java.util.logging.manager property is defined it can specify
an alternative LogManager class. If logging is used early in the startup
sequence there may be problem in accessing this LogManager class, which may
cause logging initialization to fail.
See bug 4768263 for an example of the problem.
###@###.### 2002-10-28
- relates to
-
JDK-4768263 ExceptionInInitailizerError triggered when LogManager loaded in S1AS
- Closed
-
JDK-4772993 S1appserver7 can not start with Mantis build b05
- Closed