Remko Popma created LOG4J2-1424:
-----------------------------------
Summary: Generic Message contents transfer mechanism into Async
Logger ringbuffer
Key: LOG4J2-1424
URL: https://issues.apache.org/jira/browse/LOG4J2-1424
Project: Log4j 2
Issue Type: Improvement
Components: Core
Affects Versions: 2.6
Reporter: Remko Popma
Log4j 2.6 in garbage-free mode uses a reusable message, and transfers the
message content into the AsyncLogger ringbuffer for consumption by the
background thread.
This ticket proposes to make this mechanism more general so it can be used by
custom messages.
This will involve
* Some way for users to populate the ringbuffer with either custom
RingBufferLogEvents, or by setting the Message field of the RingBufferLogEvents
to pre-allocated instances.
* Some transfer mechanism to copy the payload of a custom Message that was
logged by the appliction into the Message field of the RingBufferLogEvent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
