[
https://issues.apache.org/jira/browse/LOG4J2-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953308#comment-14953308
]
Matt Sicker commented on LOG4J2-801:
------------------------------------
The use case brought up was in Spring applications where Loggers are stored as
normal fields instead of static fields. Some beans will get cached by HTTP
session logic which requires serialization. In this case, I think a smarter
serialization method would make more sense as caching all the underlying
configuration and context objects seems to be a lot of data that is easily
recovered anytime Log4j2 is restarted.
> org.apache.logging.log4j.core.Logger should be serializable
> -----------------------------------------------------------
>
> Key: LOG4J2-801
> URL: https://issues.apache.org/jira/browse/LOG4J2-801
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0, 2.0.1, 2.0.2
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_65, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_65\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.3
>
>
> org.apache.logging.log4j.core.Logger should be serializable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
