You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2020/02/03 23:59:00 UTC
[jira] [Resolved] (LOG4J2-2770) NullPointerException after
reconfiguring via JMX
[ https://issues.apache.org/jira/browse/LOG4J2-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory resolved LOG4J2-2770.
-------------------------------------
Fix Version/s: 2.13.1
3.0.0
Resolution: Fixed
> NullPointerException after reconfiguring via JMX
> ------------------------------------------------
>
> Key: LOG4J2-2770
> URL: https://issues.apache.org/jira/browse/LOG4J2-2770
> Project: Log4j 2
> Issue Type: Bug
> Components: Core, JMX
> Affects Versions: 2.13.0
> Reporter: Bill Kuker
> Priority: Major
> Fix For: 3.0.0, 2.13.1
>
>
> Load JMX GUI, go to Log4j Tab, select context, click "Reconfigure with XML below".
> the new configuration is accepted and active, but then the subsequent call to LogerContextAdmin::getConfigText() throws an NPE.
> Looking deeper, the ConfigurationSource created in LogerContextAdmin::setConfigText(...) is created in such a way that ConfigurationSource::resetInputStream(), used by getConfigText, is unable to create a duplicate of the ConfigurationSource and instead returns null.
> The constructor {{ConfigurationSource(final byte[] data, final URL url, long lastModified) }} neglects to set the data member.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)