You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "a b (JIRA)" <ji...@apache.org> on 2019/02/26 08:05:00 UTC
[jira] [Closed] (LOG4J2-2555) Cannot get suggested method of
reconfiguring to work
[ https://issues.apache.org/jira/browse/LOG4J2-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
a b closed LOG4J2-2555.
-----------------------
Resolution: Not A Problem
Thanks. I've now managed to get the mentioned use-case working.
> Cannot get suggested method of reconfiguring to work
> ----------------------------------------------------
>
> Key: LOG4J2-2555
> URL: https://issues.apache.org/jira/browse/LOG4J2-2555
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
> Reporter: a b
> Priority: Major
>
> Hi
> Doesn't https://jira.apache.org/jira/browse/LOG4J2-2240 mean that the method of reconfiguration presented in [https://logging.apache.org/log4j/log4j-2.4/faq.html#reconfig_from_code] is broken?
> If it is broken, think it'd be best to remove it from the docs, as it gives people a bum steer.
> I cannot seem to get it to work. Is there a test in log4j that verifies Something along the line of:
> # Configures config C1.
> # Initializes logger L. Logs an event. Asserts event is logged as-per config C1.
> # Reconfigures to config C2 (e.g. changes appender pattern, modifies some other appender attribute, add/remove/modify loggers)
> # Logs event to logger L. Asserts event is logged as-per config C2.
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)