[ https://issues.apache.org/jira/browse/LOG4J2-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers updated LOG4J2-1142: -------------------------------- Attachment: LOG4J2-1142.patch Remko, I have created a patch that uses an object pool instead of thread locals. Could you give it a whirl and see how much of a performance difference there is? > ThreadLocals in Layout implementations should be non-static to prevent memory > leaks in web containers > ----------------------------------------------------------------------------------------------------- > > Key: LOG4J2-1142 > URL: https://issues.apache.org/jira/browse/LOG4J2-1142 > Project: Log4j 2 > Issue Type: Improvement > Components: Layouts > Affects Versions: 2.4 > Reporter: Dmitri Blinov > Assignee: Remko Popma > Fix For: 2.4.1 > > Attachments: LOG4J2-1142.patch > > > As discussed in LOG4J2-1125, storing ThreadLocal<StringBuilder> in a static > field may not interact well with the thread pools and class loaders of some > web containers and may result in memory leaks, especially in older web > containers. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org