You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Piotr Karwasz (Jira)" <ji...@apache.org> on 2022/03/28 09:07:00 UTC

[jira] [Assigned] (LOG4J2-3450) Add mechanism to disable Log4j2 automatic configuration

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

Piotr Karwasz reassigned LOG4J2-3450:
-------------------------------------

    Assignee: Piotr Karwasz

> Add mechanism to disable Log4j2 automatic configuration
> -------------------------------------------------------
>
>                 Key: LOG4J2-3450
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3450
>             Project: Log4j 2
>          Issue Type: Task
>            Reporter: Piotr Karwasz
>            Assignee: Piotr Karwasz
>            Priority: Minor
>
> Log4j2 automatic configuration is useful in most circumstances.
> However in specific environments it only adds some start-up time to the application. Such a specific environment is for example Spring Boot: Spring Boot reconfigures Log4j2 at a very early stage of its startup sequence, but *after* the automatic configuration. As a result Log4j2 is configured twice.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)