[
https://issues.apache.org/jira/browse/LOG4J2-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137284#comment-16137284
]
Gary Gregory edited comment on LOG4J2-2005 at 8/22/17 8:04 PM:
---------------------------------------------------------------
Hm..., to avoid breaking existing configs we could go the other way by
converting custom level names to upper case.
And too bad we cannot build the {{ConcurrentHashMap}} with
{{String.CASE_INSENSITIVE_ORDER}}...
was (Author: garydgregory):
Hm..., to avoid breaking existing configs we could go the other way by
converting custom level names to upper case.
> Level.valueOf() converts level strings to uppercase
> ---------------------------------------------------
>
> Key: LOG4J2-2005
> URL: https://issues.apache.org/jira/browse/LOG4J2-2005
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.8.2
> Reporter: Paul Burrowes
>
> When using custom levels that are not all uppercase the serialized level
> strings are not deserializable back into levels because Level.valueOf()
> assumes all levels will be uppercase.
> https://logging.apache.org/log4j/2.x/manual/customloglevels.html says that
> levels are case sensitive and the convention is to use uppercase. Having the
> convention mandatory in code breaks all cases where the level name has
> already been standardised as mixed case.
> The fix is simple, Level.valueOf() should not convert levelName to uppercase.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
