[
https://issues.apache.org/jira/browse/LOG4J2-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838028#comment-15838028
]
Matt Sicker commented on LOG4J2-1799:
-------------------------------------
Yeah, it looks like it should use {{Charset.forName(prop)}}. This is related to
LOG4J2-1636 which amusingly enough is marked as fixed in the changelog, but
open in JIRA.
> Error determining the current charset
> -------------------------------------
>
> Key: LOG4J2-1799
> URL: https://issues.apache.org/jira/browse/LOG4J2-1799
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.8
> Reporter: Vadim Lotarev
> Priority: Blocker
>
> Switching to the latest release I've immediately got the following error:
> {code}
> Unable to inject fields into builder class for plugin type class
> org.apache.logging.log4j.core.appender.ConsoleAppender, element Consol
> e. java.nio.charset.UnsupportedCharsetException: sun.stdout.encoding
> {code}
> In the PropertiesUtil I see the following:
> {code:java}
> public Charset getCharsetProperty(final String name, final Charset
> defaultValue) {
> final String prop = getStringProperty(name);
> return prop == null ? defaultValue : Charset.forName(name);
> }
> {code}
> Shouldn't {{prop}} be used in {{Charset.forName(name)}} instead of {{name}}?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
