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: Thu, 2 Jun 2016 22:19:59 +0000 (UTC)
From: "Gary Gregory (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12975290.1464900932000.20310.1464905999355@Atlassian.JIRA>
In-Reply-To: <JIRA.12975290.1464900932000@Atlassian.JIRA>
References: <JIRA.12975290.1464900932000@Atlassian.JIRA> <JIRA.12975290.1464900932073@arcas>
Subject: [jira] [Updated] (LOG4J2-1407) Misleading WARN log events from
 Log4j about message factories and unexpected formatting
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Jun 2016 22:20:01 -0000


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

Gary Gregory updated LOG4J2-1407:
---------------------------------
    Description: 
We log misleading WARN log events from Log4j about message factories and unexpected formatting.

For example:

{noformat}
2016-05-29 18:21:46,712 main WARN The Logger com.example.foo was created with the message factory org.apache.logging.log4j.spi.MessageFactory2Adapter@46bc9802 and is now requested with the message factory org.apache.logging.log4j.m
essage.StringFormatterMessageFactory@510e0dd2, which may create log events with unexpected formatting.
{noformat}

This is because in 2.6, {{AbstractMessageFactory}} implements {{MessageFactory}} instead of {{MessageFactory2}}.

This issue changes {{AbstractMessageFactory}} to implement {{MessageFactory2}}.

  was:
We log misleading WARN log events from Log4j about message factories and unexpected formatting.

For example:

{noformat}
2016-05-29 18:21:46,712 main WARN The Logger com.example.foo was created with the message factory org.apache.logging.log4j.spi.MessageFactory2Adapter@46bc9802 and is now requested with the message factory org.apache.logging.log4j.m
essage.StringFormatterMessageFactory@510e0dd2, which may create log events with unexpected formatting.
{noformat}


> Misleading WARN log events from Log4j about message factories and unexpected formatting
> ---------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1407
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1407
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 2.6
>            Reporter: Gary Gregory
>            Assignee: Gary Gregory
>             Fix For: 2.6.1
>
>
> We log misleading WARN log events from Log4j about message factories and unexpected formatting.
> For example:
> {noformat}
> 2016-05-29 18:21:46,712 main WARN The Logger com.example.foo was created with the message factory org.apache.logging.log4j.spi.MessageFactory2Adapter@46bc9802 and is now requested with the message factory org.apache.logging.log4j.m
> essage.StringFormatterMessageFactory@510e0dd2, which may create log events with unexpected formatting.
> {noformat}
> This is because in 2.6, {{AbstractMessageFactory}} implements {{MessageFactory}} instead of {{MessageFactory2}}.
> This issue changes {{AbstractMessageFactory}} to implement {{MessageFactory2}}.


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