[
https://issues.apache.org/jira/browse/LOG4J2-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751771#comment-15751771
]
Toby Shepheard commented on LOG4J2-1455:
----------------------------------------
Noticed this same issue too - the fix should be relatively straightforward,
will look to put something together.
> CompositeConfiguration Logger level not overridable
> ---------------------------------------------------
>
> Key: LOG4J2-1455
> URL: https://issues.apache.org/jira/browse/LOG4J2-1455
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.6
> Reporter: Philipp Knobel
>
> Trying to have a logger level overriden within compositeConfiguration, seems
> to be not working, see
> https://github.com/philnate/logging-log4j2/commit/e743e7c05fd282b0f75b285fe41ca18282403a2a
> It looks like that if there's already a logger we forget to copy over it's
> attribute, like we do if the targetNode doesn't exist.
--
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
