| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8269553 | 18 | Xin Liu | P3 | Resolved | Fixed | b04 |
| JDK-8270664 | 17.0.1 | Xin Liu | P3 | Resolved | Fixed | b03 |
I read JEP-158 again, here is the statement:
"Logging can be configured dynamically at runtime via jcmd or MBeans"
Currently, dcmd can change tags and decorators on the fly.
eg. The following command affects log output #2, which is file=gc.log
jcmd 120863 VM.log output=file=gc.log what='all=off,logging+thread=debug,gc=debug' decorators=t,tid,l,tags
dmcd can use 'what' and 'decorators' to change log selections and decorators. those things are changeable for an established log output.
This feature is supported well by synchronous logging. Currently, it's not MT-safe in async mode.
"Logging can be configured dynamically at runtime via jcmd or MBeans"
Currently, dcmd can change tags and decorators on the fly.
eg. The following command affects log output #2, which is file=gc.log
jcmd 120863 VM.log output=file=gc.log what='all=off,logging+thread=debug,gc=debug' decorators=t,tid,l,tags
dmcd can use 'what' and 'decorators' to change log selections and decorators. those things are changeable for an established log output.
This feature is supported well by synchronous logging. Currently, it's not MT-safe in async mode.
- backported by
-
JDK-8269553 async logging supports to dynamically change tags and decorators
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
JDK-8269237 gtest/AsyncLogGtest.java failed with "assert(_decorators.is_decorator(decorator)) failed: decorator was not part of the decorator set specified at creation."
-
- Closed
-
- relates to
-
JDK-8229517 Support for optional asynchronous/buffered logging
-
- Resolved
-
(2 links to)