[LOG4J2-1099] AbstractStringLayout implements Serializable, but is not Serializable

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.3
• Component/s: Layouts
• Assignee: Matt Sicker
• Reporter: Louis Burton
• Created: 20/Aug/15 17:29
• Updated: 12/Oct/15 17:59
• Resolved: 11/Oct/15 23:21

Description

org.apache.logging.log4j.core.layout.AbstractLayout line 34 :

    // TODO: Charset is not serializable. Implement read/writeObject() ?
    private final Charset charset;

The developer has recognised that this class claims to be serializable, but is not actually serializable.

This actually has wide impact due to the fact that the Logger is holding onto the Layout via the org.apache.logging.log4j.core.Logger.PrivateConfig#config (XML in my case). Many projects, including Spring, do not use static Loggers and prefer getClass type approaches off of their abstract classes, i.e.:

protected final Log logger = LogFactory.getLog(getClass());

This actually can lead to use of spring session beans, which are serialized with the session, trying to serialize the logger also and failing due to this bug.

Issue Links

• duplicates: LOG4J2-801 org.apache.logging.log4j.core.Logger should be serializable
• is required by: LOG4J2-801 org.apache.logging.log4j.core.Logger should be serializable