You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/05/17 15:34:12 UTC

[jira] [Resolved] (LOG4J2-1348) Add an AutoCloseable ThreadContext class: CloseableThreadContext

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

Remko Popma resolved LOG4J2-1348.
---------------------------------
    Resolution: Fixed

Applied latest "instance" patch to master in commit 7fca94f.

CloseableThreadContext now returns an instance that allows chained method calls like CloseableThreadContext.put(key, value).put(anotherKey, anotherValue);




> Add an AutoCloseable ThreadContext class: CloseableThreadContext
> ----------------------------------------------------------------
>
>                 Key: LOG4J2-1348
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1348
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>            Reporter: Greg Thomas
>            Assignee: Gary Gregory
>            Priority: Minor
>             Fix For: 2.6
>
>         Attachments: CloseableThreadContext.zip, ctc-also.patch, ctc-instance.patch, ctc.patch, thread-context.xml.patch
>
>
> The log4j2 API provides a ThreadContext - https://logging.apache.org/log4j/2.x/manual/thread-context.html -  that allows items to be added to a stack or a map for logging, and then subsequently removed once they are no longer required.
> This sounds like an ideal candidate for a AutoCloseable implementation so that items are removed automatically and no longer left around littering the stack/map.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org