[LOG4J2-1556] Custom Log4j threads should extend Log4jThread

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Component/s: Core, Flume Appender
• Assignee: Gary D. Gregory
• Reporter: Gary D. Gregory
• Created: 31/Aug/16 20:35
• Updated: 31/Aug/16 20:37
• Resolved: 31/Aug/16 20:37

Description

Custom Log4j threads should extend org.apache.logging.log4j.core.util.Log4jThread instead of java.lang.Thread to allow Log4jThread to prefix thread names with "Log4j2-", thus making Log4j threads easier to identify in thread dumps and debuggers.

This patch applies to:

• org.apache.logging.log4j.core.appender.AsyncAppender.AsyncThread
• org.apache.logging.log4j.flume.appender.FlumePersistentManager.WriterThread
• org.apache.logging.log4j.core.net.TcpSocketManager.Reconnector
• org.apache.logging.log4j.core.net.server.TcpSocketServer.SocketHandler