-
Sub-task
-
Resolution: Delivered
-
P3
-
25
The debug output from the `java.security.debug` system property now includes thread id, caller information, and timestamp information.
Each debug output statement generated via the java.security.debug option is now formatted as:
`componentValue[threadId|threadName|sourceCodeLocation|timestamp]: <debug statement>`
where:
* `componentValue` is the security component value being logged.
* `threadId` is the hexadecimal value of the thread ID.
* `threadName` is the name of the thread executing the log statement.
* `sourceCodeLocation` is the source file and line number making this log call, in the format "filename:lineNumber".
* `timestamp` is the date and time in the format "yyyy-MM-dd kk:mm:ss.SSS".
* <debug statement> corresponds to the debug output from the security component.
The `+thread` and `+timestamp` options introduced in JDK 23 will no longer have an impact and are ignored.
More information on those legacy options is available in the [JDK 23 release notes](https://www.oracle.com/java/technologies/javase/23-relnote-issues.html#JDK-8051959).
Each debug output statement generated via the java.security.debug option is now formatted as:
`componentValue[threadId|threadName|sourceCodeLocation|timestamp]: <debug statement>`
where:
* `componentValue` is the security component value being logged.
* `threadId` is the hexadecimal value of the thread ID.
* `threadName` is the name of the thread executing the log statement.
* `sourceCodeLocation` is the source file and line number making this log call, in the format "filename:lineNumber".
* `timestamp` is the date and time in the format "yyyy-MM-dd kk:mm:ss.SSS".
* <debug statement> corresponds to the debug output from the security component.
The `+thread` and `+timestamp` options introduced in JDK 23 will no longer have an impact and are ignored.
More information on those legacy options is available in the [JDK 23 release notes](https://www.oracle.com/java/technologies/javase/23-relnote-issues.html#JDK-8051959).