[
https://issues.apache.org/jira/browse/LOG4J2-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222632#comment-15222632
]
Remko Popma commented on LOG4J2-1347:
-------------------------------------
Also, any reason to prefer AsyncAppender to Async Loggers? Note that the [mixed
form of Async
Loggers|http://logging.apache.org/log4j/2.x/manual/async.html#MixedSync-Async]
is implemented to use the LogEvent produced by the factory all the way through
to the layout. So there is no loss of information here. (But this may change
when LOG4J2-1334 is implemented, so we should coordinate if you're interested
in using Async Loggers.)
> AsyncAppender - Allow serialization of custom LogEvents
> -------------------------------------------------------
>
> Key: LOG4J2-1347
> URL: https://issues.apache.org/jira/browse/LOG4J2-1347
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: John Strickler
> Priority: Minor
>
> This request is for an improvement to AsyncAppender to allow sublasses of
> Log4jLogEvent to be serialized without losing their specific type.
> The current functionality is that AsyncAppender will serialize all subclasses
> back to a true instance of Log4jLogEvent. In the process, all extra
> information is lost that was provided by the subclass.
> _AsyncAppender, line 156:_
> bq. final Serializable serialized = Log4jLogEvent.serialize(coreEvent,
> includeLocation);
> *Use Case*
> Subclasses of Log4jLogEvent that contain the authenticated principal to be
> logged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
