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 "Matt Sicker (JIRA)" <ji...@apache.org> on 2017/04/02 17:53:42 UTC
[jira] [Resolved] (LOG4J2-1861) Fix JavaDoc on
org.apache.logging.log4j.ThreadContext (about inheritance)
[ https://issues.apache.org/jira/browse/LOG4J2-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker resolved LOG4J2-1861.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.8.2
Fixed in master. Please verify and close.
> Fix JavaDoc on org.apache.logging.log4j.ThreadContext (about inheritance)
> -------------------------------------------------------------------------
>
> Key: LOG4J2-1861
> URL: https://issues.apache.org/jira/browse/LOG4J2-1861
> Project: Log4j 2
> Issue Type: Documentation
> Components: API
> Affects Versions: 2.8.1
> Reporter: Franz van Betteraey
> Assignee: Matt Sicker
> Priority: Trivial
> Labels: easyfix, javadoc
> Fix For: 2.8.2
>
>
> The [JavaDoc|https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/ThreadContext.html] of org.apache.logging.log4j.ThreadContext describes the behavior regarding inheritance as follows:
> {quote}
> A child thread automatically inherits a copy of the mapped diagnostic context of its parent.
> {quote}
> But the behavior was changed in LOG4J2-479. Now the system property _isThreadContextMapInheritable_ has to be set to _true_ to enforce this behavior (see [documentation|https://logging.apache.org/log4j/2.x/manual/thread-context.html]). This should be corrected in the JavaDoc of ThreadContext.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org