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

Posted to issues@ignite.apache.org by "Alexey Kukushkin (Jira)" <ji...@apache.org> on 2022/05/12 07:20:00 UTC

[jira] [Updated] (IGNITE-16716) Ignite JUL Logger should not change the configuration

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

Alexey Kukushkin updated IGNITE-16716:
--------------------------------------
    Remaining Estimate: 168h
     Original Estimate: 168h

> Ignite JUL Logger should not change the configuration
> -----------------------------------------------------
>
>                 Key: IGNITE-16716
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16716
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Kukushkin
>            Priority: Major
>              Labels: cggg
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Ignite's {{JavaLogger}} forcefully re-configures logging by adding/removing appenders and changing severity based on some system properties and environment variables.
> This makes it hard or even impossible to consistently switch between different loggers keeping the same level of output.
> Please enhance the {{JavaLogger}} to no mess with the configuration or explain why that cannot be done



--
This message was sent by Atlassian Jira
(v8.20.7#820007)