Description
Until now I kept the scope of the garbage-free logging epic LOG4J2-1270 limited to asynchronous logging with all loggers asynchronous. This seemed a natural thing to do since async loggers already have pre-allocated all LogEvent instances.
Now that LOG4J2-1270 is nearing completion it looks as if the only thing that is required to allow synchronous logging to be garbage-free is a reusable LogEvent implementation, stored in a ThreadLocal. This ticket is to analyse and track the work for this option.
Attachments
Attachments
Issue Links
- is related to
-
LOG4J2-1347 AsyncAppender - Allow serialization of custom LogEvents
- Resolved