ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirill Danilov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-7116) Logging minor issue as error instead of warning or info
Date Tue, 05 Dec 2017 17:01:00 GMT

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

Kirill Danilov updated IGNITE-7116:
-----------------------------------
    Description: 
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.

  was:
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 to load. 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.


> 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
>         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
(v6.4.14#64029)

Mime
View raw message