Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3521296AA for ; Tue, 1 May 2012 04:26:12 +0000 (UTC) Received: (qmail 19246 invoked by uid 500); 1 May 2012 04:26:11 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 19186 invoked by uid 500); 1 May 2012 04:26:11 -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 19177 invoked by uid 99); 1 May 2012 04:26:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2012 04:26:11 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2012 04:26:09 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 6C2FE429BC4 for ; Tue, 1 May 2012 04:25:48 +0000 (UTC) Date: Tue, 1 May 2012 04:25:48 +0000 (UTC) From: "Ralph Goers (JIRA)" To: log4j-dev@logging.apache.org Message-ID: <662081653.12386.1335846348492.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (LOG4J2-21) LoggingEvent message lost on serialization MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4J2-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-21. ------------------------------- Resolution: Fixed Fix Version/s: 2.0-alpha1 Assignee: Ralph Goers This is an inherent part of the Log4j 2 architecture. > LoggingEvent message lost on serialization > ------------------------------------------ > > Key: LOG4J2-21 > URL: https://issues.apache.org/jira/browse/LOG4J2-21 > Project: Log4j 2 > Issue Type: Wish > Components: Appenders > Reporter: Curt Arnold > Assignee: Ralph Goers > Fix For: 2.0-alpha1 > > > log4j bug 42023 complained that the LoggingEvent serialization did not attempt to serialize the message object, but only serialized the rendered message. Whatever serialized forms are supported in log4j 2.0 should provide the option to transmit a serialized form of the message object. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org