You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2015/08/11 10:46:45 UTC
[jira] [Updated] (IGNITE-1228) Invalid logger behavior when log4j
configuration cannot be found
[ https://issues.apache.org/jira/browse/IGNITE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Setrakyan updated IGNITE-1228:
--------------------------------------
Priority: Blocker (was: Critical)
> Invalid logger behavior when log4j configuration cannot be found
> ----------------------------------------------------------------
>
> Key: IGNITE-1228
> URL: https://issues.apache.org/jira/browse/IGNITE-1228
> Project: Ignite
> Issue Type: Bug
> Components: general
> Reporter: Alexey Goncharuk
> Assignee: Valentin Kulichenko
> Priority: Blocker
> Fix For: ignite-1.4
>
>
> In my tests I started Ignite without a valid log4j configuration file in QUIET mode, this is what I've got in the console:
> {code}
> log4j:WARN No appenders could be found for logger (org.apache.ignite.internal.util.typedef.G).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> [00:14:29] __________ ________________
> [00:14:29] / _/ ___/ |/ / _/_ __/ __/
> [00:14:29] _/ // (7 7 // / / / / _/
> [00:14:29] /___/\___/_/|_/___/ /_/ /___/
> [00:14:29]
> [00:14:29] ver. 1.3.3#20150803-sha1:7d747d2a
> [00:14:29] 2015 Copyright(C) Apache Software Foundation
> [00:14:29]
> [00:14:29] Ignite documentation: http://ignite.incubator.apache.org
> [00:14:29]
> [00:14:29] Quiet mode.
> [00:14:29] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or "-v" to ignite.{sh|bat}
> [00:14:29]
> [00:14:29] Configured plugins:
> [00:14:29] ^-- None
> [00:14:29]
> [00:14:31] Security status [authentication=off, communication encryption=off]
> [00:14:34] Performance suggestions for grid 'Benchmark' (fix if possible)
> [00:14:34] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [00:14:34] ^-- Disable grid events (remove 'includeEventTypes' from configuration)
> [00:14:34]
> [00:14:34] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
> [00:14:34]
> [00:14:34] Ignite node started OK (id=96b97d66, grid=Benchmark)
> [00:14:34] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=3.0GB]
> {code}
> When I ran micro-benchmarks in this configuration, it turned out that 90% time is spent in building strings for logger. I checked and {{ignite.log().isDebugEnabled()}} returned {{true}}, which is a serious user experience issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)