ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evgenii Zhuravlev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8426) Some classes creates JavaLogger directly which lead to SEVERE message in logs if JUL config file is missing
Date Thu, 28 Jun 2018 15:31:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526434#comment-16526434
] 

Evgenii Zhuravlev commented on IGNITE-8426:
-------------------------------------------

[~agoncharuk], added stopping of LongJVMPauseDetector on node stop

> 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
>            Assignee: Evgenii Zhuravlev
>            Priority: Blocker
>             Fix For: 2.7
>
>
> 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)

Mime
View raw message