You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2021/08/28 19:41:00 UTC

[jira] [Assigned] (LOG4J2-2433) Support MDCs with Kotlin coroutines

     [ https://issues.apache.org/jira/browse/LOG4J2-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker reassigned LOG4J2-2433:
-----------------------------------

    Assignee:     (was: Raman Gupta)

> Support MDCs with Kotlin coroutines
> -----------------------------------
>
>                 Key: LOG4J2-2433
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2433
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Kotlin API
>    Affects Versions: Kotlin 1.0.0
>            Reporter: Raman Gupta
>            Priority: Major
>             Fix For: Kotlin 1.1.0
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Create support for log4j2 MDC when used with Kotlin coroutines. Since coroutines do not guarantee which underlying thread is executing code after a continuation, a standard ThreadLocal is not sufficient to keep the MDC context.
> Kotlin coroutines have a mechanism by which "coroutine local" data can be stored. See the reference implementation for SLF4J here:
> https://github.com/Kotlin/kotlinx.coroutines/tree/master/integration/kotlinx-coroutines-slf4j
> We should implement an optional native module to add support for log4j2 MDC using the same pattern, that does not require having SLF4J and the slf4j-log4j2 implementation on the classpath.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)