[LOG4J2-1663] Ensure SortedArrayStringMap can be serialized/deserialized regardless of content

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.8
• Component/s: API
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 05/Nov/16 16:07
• Updated: 17/Jun/17 02:27
• Resolved: 05/Nov/16 16:26

Description

Improve the implementation of SortedArrayStringMap serialization logic to ensure that serializing or deserializing it never results in an error, regardless of the content.

• Values that are not Serializable should be replaced with null in the serialized form
• When the class of a value is not available at the time the SortedArrayStringMap is deserialized, the value should be replaced with null in the deserialized object.

Issue Links

• breaks: LOG4J2-1926 Remove dependency on RMI and Management APIs from log4j-api
• is depended upon by: LOG4J2-1648 Provide ability for users to put non-String values in the ThreadContext
• is related to: LOG4J2-1226 Message instances are simply serialized. They mustn't.