[
https://issues.apache.org/jira/browse/IGNITE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Shutak updated IGNITE-923:
--------------------------------
Summary: IgniteJclLogger.isQuiet() implementation has a bug. (was: There
are messages printed at System.out directly instead of JavaLogger.)
> IgniteJclLogger.isQuiet() implementation has a bug.
> ---------------------------------------------------
>
> Key: IGNITE-923
> URL: https://issues.apache.org/jira/browse/IGNITE-923
> Project: Ignite
> Issue Type: Bug
> Reporter: Artem Shutak
> Priority: Minor
>
> The bug is based on user ticket:
> http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330.
> There are some places at code where Ignite print messages directly at
> System.out instead of IgniteLogger.
> Need to print all messages at logger.
> There are a workflow (to disable all Ignite messages): need to delete
> appenderes for "org.apache.ignite".
> For example (JCL with log4j2.):
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <Configuration status="WARN">
> <Appenders>
> <Console name="Console" target="SYSTEM_OUT">
> <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level
> %logger{36} - %msg%n"/>
> </Console>
> </Appenders>
> <Loggers>
> <Logger name="org.apache.ignite" level="DEBUG" additivity="false">
> <!--Don't log at console.-->
> </Logger>
> <Root level="DEBUG">
> <AppenderRef ref="Console"/>
> </Root>
> </Loggers>
> </Configuration>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
