[
https://issues.apache.org/jira/browse/IGNITE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526407#comment-16526407
]
Alexey Goncharuk commented on IGNITE-8426:
------------------------------------------
[~ezhuravl], after your fix, if I start and shut down Ignite nodes in a loop, I
will end up with multiple daemon threads started, but not stopped, each of them
printing out the same output to the log + this is a major resource leak in
tests.
Please fix the thread lifecycle.
> 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)
