-
Enhancement
-
Resolution: Fixed
-
P3
-
None
-
generic
-
generic
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.
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.
- relates to
-
JDK-8148188 Enhance the security libraries to record events of interest
- Resolved
-
JDK-7013776 Multithreaded JSSE application debug information is hard to read
- Closed