Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Tue, 30 Aug 2016 00:20:20 +0000 (UTC)
From: "Remko Popma (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12828285.1431073845000.442305.1472516420569@Atlassian.JIRA>
In-Reply-To: <JIRA.12828285.1431073845000@Atlassian.JIRA>
References: <JIRA.12828285.1431073845000@Atlassian.JIRA> <JIRA.12828285.1431073845268@arcas>
Subject: [jira] [Commented] (LOG4J2-1010) Injectable context properties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 30 Aug 2016 00:20:22 -0000


    [ https://issues.apache.org/jira/browse/LOG4J2-1010?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D154=
47531#comment-15447531 ]=20

Remko Popma commented on LOG4J2-1010:
-------------------------------------

The performance concerns Ralph raised regarding global Filters have been ad=
dressed.

For further reviews, may I propose that people review the {{LOG4J2-1349-gcf=
ree-threadcontext}} branch instead? It has the same changes as the {{LOG4J2=
-1010&LOG4J2-1447-injectable-contextdata&better-datastructure}} branch, but=
 in addition moved ContextData and related interfaces to org.apache.logging=
.log4j.spi package in log4j-api.

Without the LOG4J2-1349 changes
* context data-based Filters and Lookups need to make an unnecessary copy
* injecting context data into the log event needs to make an unnecessary co=
py

> Injectable context properties
> -----------------------------
>
>                 Key: LOG4J2-1010
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1010
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.2
>            Reporter: Mikael St=C3=A5ldal
>            Assignee: Remko Popma
>             Fix For: 2.7
>
>         Attachments: properties.patch
>
>
> It would be useful to have a way to inject context properties into a {{Lo=
gEvent}}, as an alternative to {{ThreadContext}}.
> In an asynchronous environment, using ThreadContext as currently implemen=
ted is not so useful since JVM threads might not be coupled to the logical =
flow of the application.


--
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