logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (LOG4J2-1799) Error determining the current charset
Date Thu, 02 Feb 2017 16:43:51 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remko Popma reassigned LOG4J2-1799:
-----------------------------------

    Assignee: Remko Popma

> 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
>            Assignee: Remko Popma
>            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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message