JDK-8019853 : Break logging and AWT circular dependency
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.util.logging
  • Affected Version: 7u25
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-07-03
  • Updated: 2014-02-07
  • Resolved: 2013-09-04
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.
7u55Fixed 8 b108Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
TimeZone and logging are the two core libraries components that maintain a global state across a running JVM and was not designed for applets isolation.   To support applets isolation, the implementation has changed to maintain per-AppContext content that introduced the dependency from core-libs to sun.awt.AppContext class through sun.misc.JavaAWTAccess.

Logging uses AWT and timezone whereas AWT uses logging that will call timezone for the default log message format.  This circular dependency is error-prone and hard to diagnose (JDK-8014718).

JDK-8001029 will remove the dependency on AppContext.  This bug is to break the logging / awt circular dependency on the lazy initialization of sun.awt.AppContext.

See also test case in JDK-8023258