Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1ED23200B29 for ; Thu, 30 Jun 2016 10:30:12 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1D6D0160A52; Thu, 30 Jun 2016 08:30:12 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 65FD7160A51 for ; Thu, 30 Jun 2016 10:30:11 +0200 (CEST) Received: (qmail 44847 invoked by uid 500); 30 Jun 2016 08:30:10 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 44833 invoked by uid 99); 30 Jun 2016 08:30:10 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2016 08:30:10 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 51FBB2C02A4 for ; Thu, 30 Jun 2016 08:30:10 +0000 (UTC) Date: Thu, 30 Jun 2016 08:30:10 +0000 (UTC) From: =?utf-8?Q?Mikael_St=C3=A5ldal_=28JIRA=29?= To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (LOG4J2-1452) Reusable messages break flow tracing logic MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 30 Jun 2016 08:30:12 -0000 [ https://issues.apache.org/jira/browse/LOG4J2-1452?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D153= 56735#comment-15356735 ]=20 Mikael St=C3=A5ldal commented on LOG4J2-1452: ---------------------------------------- Removing test since it was not well received. > Reusable messages break flow tracing logic > ------------------------------------------ > > Key: LOG4J2-1452 > URL: https://issues.apache.org/jira/browse/LOG4J2-1452 > Project: Log4j 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.6, 2.6.1 > Reporter: Mikael St=C3=A5ldal > Assignee: Remko Popma > Fix For: 2.6.2 > > > Flow tracing assumes that you can save an instance of {{EntryMessage}} ac= ross a method, but if you log something else within that method and reusabl= e messages are in effect (as they are by default since 2.6), this does not = always work properly. > This code illustrate the issue: > {code} > EntryMessage entryMessage =3D logger.traceEntry(logger.getMessage= Factory().newMessage("the entry")); > logger.info("something else"); > logger.traceExit(entryMessage); > {code} > It works as expected if you remove the middle {{logger.info()}}, but with= it the exit message gets messed up. -- 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