JDK-4747357 : Logging should be initialized lazily
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-09-13
  • Updated: 2002-10-25
  • Resolved: 2002-10-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 mantisFixed
Related Reports
Relates :  
JDK-4757212 - JVM 1.4.2 regression on Sierra EE startup compared to JVM 1.3.1 in mixed mode
Description
Investigation into traces of J2SE startup time has shown a significant
amount of time being spent in initialization of the logging
subsystem. Initialization of logging was added to the core
java.lang.System.initializeSystemClass() routine in 1.4.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b05
14-06-2004
WORK AROUND
11-06-2004
SUGGESTED FIX
11-06-2004
PUBLIC COMMENTS
10-06-2004
EVALUATION Making the initialization of this package lazy eliminates its loading by the core libraries for non-GUI applications and decreases the startup time for a Hello, World application by about 6.9%. Implemented in 1.4.2. ###@###.### 2002-09-13
13-09-2002