[
https://issues.apache.org/jira/browse/IGNITE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525094#comment-16525094
]
Evgenii Zhuravlev commented on IGNITE-8426:
-------------------------------------------
Looks like JDBC Driver is a standalone component and this is ok to have such
error for it, since it should have explicit logger configuration.
As for LongJvmPauseDetector - It was static and out of Ignite context. I had to
add IgniteLogger to it and make it non-static.
> 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)
