JDK-6708508 : LogManager.readConfiguration() throws an exception
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2008-05-29
  • Updated: 2011-01-19
  • Resolved: 2009-05-13
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.
6u14 b02Fixed
Related Reports
Relates :  
Calling LogManager.getLogManager().readConfiguration() fails on a fresh install of JKernel JRE.

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u14/6708508.0

EVALUATION Also moved rarely used CMM profiles to separate bundle to redue download footprint for some scenarios.

EVALUATION this property file is tiny and easiest thing is to include it into core bundle.

EVALUATION according to exception text "lib/logging.properties" is missing This file is not an optional feature, is it?