[
https://issues.apache.org/jira/browse/LOG4J2-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623152#comment-17623152
]
liuxichen commented on LOG4J2-3622:
-----------------------------------
I noticed almost every Java log framework has used ThreadLocal for holding
variables, also the information of thread-name are always printed, however in
virtual threads they are totally different, so I think this should be a big
fix, by changing the way we judge threads before, maybe create a new version
for it
> Support for virtual threads
> ---------------------------
>
> Key: LOG4J2-3622
> URL: https://issues.apache.org/jira/browse/LOG4J2-3622
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Reporter: liuxichen
> Priority: Critical
>
> I noticed in ReusableMessageFactory threadlocal are used, so If a am using
> jdk19 virtual threads while logging with threadlocal disabled,
> UnsupportedOperationException would be thrown, and using log in a lot of
> virtual threads might create a lot of useless objects, could you please fix
> this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
