ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Shutak (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-121) Fallback to Java logging in case of wrong Log4j version
Date Sat, 31 Jan 2015 11:57:34 GMT

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

Artem Shutak reassigned IGNITE-121:
-----------------------------------

    Assignee: Artem Shutak

> 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-2
>
>
> 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)

Mime
View raw message