[
https://issues.apache.org/jira/browse/IGNITE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520507#comment-16520507
]
ASF GitHub Bot commented on IGNITE-8426:
----------------------------------------
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/4249
IGNITE-8426 LongJVMPauseDetector add logger from context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8426
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4249.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4249
----
----
> 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)
