You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2018/05/22 15:00:00 UTC

[jira] [Assigned] (IGNITE-7116) Logging minor issue as error instead of warning or info

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

Dmitriy Pavlov reassigned IGNITE-7116:
--------------------------------------

    Resolution: Fixed
      Assignee: Kirill Danilov

[~Donz], thank you, I've merged change to master
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=d52bfdb172ae447fd1e391e7e6dd62018fb9579f

[~EdShangGG] thank you for review.

> Logging minor issue as error instead of warning or info
> -------------------------------------------------------
>
>                 Key: IGNITE-7116
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7116
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.3
>            Reporter: Kirill Danilov
>            Assignee: Kirill Danilov
>            Priority: Major
>             Fix For: 2.6
>
>         Attachments: 0001-IGNITE-7116-Decrease-logging-level-for-minor-problem.patch
>
>
> In case of using Ignite with Tomcat and its connection pool Tomcat tries to lookup for every JDBC driver that it can found. So IgniteJdbcDriver is loaded too. And this class has field
> {code:java}
> private static final IgniteLogger LOG = new JavaLogger();
> {code}
> which leads to JavaLogger loading and initialization. And in method
> {code:java}
> org.apache.ignite.logger.java.JavaLogger#defaultConfiguration
> {code}
>  there is try to get logging configuration from default file which is absent. So we get 
> {code:java}
> error("Failed to resolve default logging config file: " + DFLT_CONFIG_PATH);
> {code}
> in logs and this is very annoying as any log analyzer begins to cry about errors during startup.
> But really this error doesn't affect anything.
> So I offer to use warning instead of error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)