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: Sat, 14 Jun 2014 08:30:02 +0000 (UTC)
From: "Remko Popma (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12721239.1402734599534.131841.1402734601995@arcas>
In-Reply-To: <JIRA.12721239.1402734599534@arcas>
References: <JIRA.12721239.1402734599534@arcas>
Subject: [jira] [Created] (LOG4J2-668) AsyncAppender ignores
 RingBufferLogEvents from AsyncLoggers (when all loggers async by setting
 context selector)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Remko Popma created LOG4J2-668:
----------------------------------

             Summary: AsyncAppender ignores RingBufferLogEvents from AsyncLoggers (when all loggers async by setting context selector)
                 Key: LOG4J2-668
                 URL: https://issues.apache.org/jira/browse/LOG4J2-668
             Project: Log4j 2
          Issue Type: Bug
          Components: Appenders, Core
    Affects Versions: 2.0-rc1
            Reporter: Remko Popma
            Priority: Minor


AsyncAppender's #append method currently has this code:
{code}
if (!(logEvent instanceof Log4jLogEvent)) {
    return; // only know how to Serialize Log4jLogEvents
}
{code}

When all loggers are made asynchronous by setting Log4jContextSelector to {{org.apache.logging.log4j.core.async.AsyncLoggerContextSelector}}, they produce {{RingBufferLogEvent}} instances, not {{Log4jLogEvent}}. These log events will be dropped by AsyncAppender.


--
This message was sent by Atlassian JIRA
(v6.2#6252)

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