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

[jira] [Updated] (IGNITE-8426) Some classes creates JavaLogger directly which lead to SEVERE message in logs if JUL config file is missing

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

Evgenii Zhuravlev updated IGNITE-8426:
--------------------------------------
    Description: 
Here is the error message:

SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

For example, problem code is placed in LongJVMPauseDetector and IgniteJdbcDriver classes.

Reproducer:
IgniteConfiguration configuration = new IgniteConfiguration();
configuration.setGridLogger(new Slf4jLogger(LoggerFactory.getLogger("ignite")));
Ignition.start(configuration);

  was:
Here is the error message:

SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

For example, problem code is placed in LongJVMPauseDetector and IgniteJdbcDriver classes.


> Some classes creates JavaLogger directly which lead to SEVERE message in logs if JUL config file is missing
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8426
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8426
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Evgenii Zhuravlev
>            Priority: Minor
>
> Here is the error message:
> SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties
> For example, problem code is placed in LongJVMPauseDetector and IgniteJdbcDriver classes.
> Reproducer:
> IgniteConfiguration configuration = new IgniteConfiguration();
> configuration.setGridLogger(new Slf4jLogger(LoggerFactory.getLogger("ignite")));
> Ignition.start(configuration);



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