[
https://issues.apache.org/jira/browse/IGNITE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526289#comment-16526289
]
Evgenii Zhuravlev edited comment on IGNITE-8426 at 6/28/18 1:03 PM:
--------------------------------------------------------------------
[~EdShangGG], There is a config file for JUL in Ignite sources, so, I will need
to remove it for reproducing this error right from source code. I don't think
that it's a good idea. I've implemented another one - added debug message that
LongJVMPauseDetector was started successfully. If we see this message in
GridLogger, then it was configured properly. Please check
LongJVMPauseDetectorTest.
was (Author: ezhuravl):
[~EdShangGG], There is a config file for JUL in Ignite, so, I will need to
remove it for reproducing this error right from source code. I don't think that
it's a good idea. I've implemented another one - added debug message that
LongJVMPauseDetector was started successfully. If we see this message in
GridLogger, then it was configured properly. Please check
LongJVMPauseDetectorTest.
> 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)
