Louis Burton created LOG4J2-1099:
------------------------------------
Summary: AbstractStringLayout implements Serializable, but is not
Serializable
Key: LOG4J2-1099
URL: https://issues.apache.org/jira/browse/LOG4J2-1099
Project: Log4j 2
Issue Type: Bug
Components: Layouts
Affects Versions: 2.3
Reporter: Louis Burton
Priority: Critical
{{org.apache.logging.log4j.core.layout.AbstractLayout}} line 34 :
{code}
// TODO: Charset is not serializable. Implement read/writeObject() ?
private final Charset charset;
{code}
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.:
{code}
protected final Log logger = LogFactory.getLog(getClass());
{code}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
