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

Posted to dev@ignite.apache.org by "Artem Shutak (JIRA)" <ji...@apache.org> on 2015/02/03 11:24:34 UTC

[jira] [Closed] (IGNITE-121) Fallback to Java logging in case of wrong Log4j version

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

Artem Shutak closed IGNITE-121.
-------------------------------

> Fallback to Java logging in case of wrong Log4j version
> -------------------------------------------------------
>
>                 Key: IGNITE-121
>                 URL: https://issues.apache.org/jira/browse/IGNITE-121
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: sprint-1
>            Reporter: Alexey Goncharuk
>            Assignee: Artem Shutak
>             Fix For: sprint-1
>
>
> When no logger is configured and different version of log4j is present in classpath, {{addLog4jNoOpLogger()}} will throw an exception (due to class change or invalid argument type, for example). This leads to Ignite start error.
> The correct behavior would be to catch these errors and fallback to standard Java logging which is a default behavior when no log4j classes are available in classpath.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)