[
https://issues.apache.org/jira/browse/LOG4J2-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221532#comment-15221532
]
Remko Popma commented on LOG4J2-1343:
-------------------------------------
By addressing this issue at the AbstractOutputStreamAppender and
OutputStreamManager level, all of these appenders would support garbage-free
logging:
* ConsoleAppender
* FileAppender (need to take some care with the existing buffering logic)
* RollingFileAppender (need to take some care with the existing buffering
logic)
* TcpSocketAppender
* DatagramSocketAppender
RandomAccessFileAppender and its Rolling variant already have a ByteBuffer so
their implementation is different.
TBD: MemoryMappedFileAppender should be able to just expose the underlying
MappedByteBuffer as the destination (the potential remapping is why the
{{drain}} method returns a ByteBuffer).
> Update ConsoleAppender to utilize gc-free Layout method
> -------------------------------------------------------
>
> Key: LOG4J2-1343
> URL: https://issues.apache.org/jira/browse/LOG4J2-1343
> Project: Log4j 2
> Issue Type: Improvement
> Components: Appenders
> Affects Versions: 2.5
> Reporter: Remko Popma
>
> TBD: would we want to include this in the upcoming 2.6 release?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
