JDK-8146635 : Introduce Logger API for security libs diagnostics
  • Type: Enhancement
  • Component: security-libs
  • Priority: P3
  • Status: In Progress
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2015-11-17
  • Updated: 2019-03-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.
Related Reports
Relates :  
Relates :  
Currently, we use different flags to turn on verbose logging and tracing in various JDK components. We should look to unify verbose logging by using the Logger API. End users can turn on logging via the standard Logger mechanism. 

javax.net.debug=x and java.security.debug=y are two examples of customized debugging options used in security libs. There's no reason we can't use the Logger API to capture messages in these code areas. Logger is a more common standard for capturing debug output in enterprise apps.

Core libs sustaining is looking at possibility of converting all tracing and diagnostic flags to a 'logger' type framework. To start, we'll concentrate on security-libs as a proof of concept. We'll also continue to support the legacy debug flags for now.