More detailed answer:
1. To enable log4j
- at ignite.{sh|bat} case, just copy ignite-log4j directory from
libs/optional to libs/. 
- if you use maven, then add maven dependency

        <dependency>
            <groupId>org.apache.ignite</groupId>
            <artifactId>ignite-log4j</artifactId>
            <version>${ignite.version}</version>
        </dependency>

2. If you want use java logging then see at
config/java.util.logging.properties and provide your own configuration. From
the file comments:

#       Default java.util.logging configuration for Ignite.
#
# To use another config file use `java.util.logging.config.file` system
# property. For example `java -Djava.util.logging.config.file=myfile`

3. For more information about options which you are use, see at
org.apache.ignite.IgniteSystemProperties documentation. For example, javadoc
for IGNITE_QUIET says:

     * Set to either true or false to enable or disable quiet mode
     * of Ignite. In quiet mode, only warning and errors are printed into
the log
     * additionally to a shortened version of standard output on the start.
     * 
     * Note that if you use ignite.{sh|bat} scripts to start Ignite they
     * start by default in quiet mode. You can supply -v flag to override
it.
 




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-tp310p320.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to