RFR: 8350689: Turn on timestamp and thread metadata by default for java.security.debug [v2]

[Sean Coffey]

On Fri, 30 May 2025 14:26:14 GMT, Sean Mullan <mullan at openjdk.org> wrote:

> What is the behavior if someone had added these options in JDK 23 and is now debugging the same code with JDK 25? Are they ignored? The CSR should also note the behavior.

I've added this clarification to the CSR:

`Continued use of the +thread and +timestamp options will no longer have impact. The thread and timestamp data is always printed and valid security components used in the java.security.debug property will continue to be logged.`

> src/java.base/share/classes/java/security/doc-files/debug-system-property.html line 55:
> 
>> 53:     system property, which determines what trace messages are printed during
>> 54:     execution. The value of the property is one or more options separated by a
>> 55:     comma.
> 
> I suggest we add a sentence to this paragraph noting that each trace message also includes the thread id, timestamp, and caller information.

Thanks. Added 

"Each trace message includes the thread id, timestamp and caller information."  to this paragraph

-------------

PR Comment: https://git.openjdk.org/jdk/pull/25528#issuecomment-2922595888
PR Review Comment: https://git.openjdk.org/jdk/pull/25528#discussion_r2116063732