[
https://issues.apache.org/jira/browse/IGNITE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693891#comment-14693891
]
tc_commenter commented on IGNITE-1228:
--------------------------------------
There was triggered next test builds for last attached patch-file:
01. http://204.14.53.152/viewQueued.html?itemId=97407 - -> Run All
02. http://204.14.53.152/viewQueued.html?itemId=97408 - Ignite AOP
03. http://204.14.53.152/viewQueued.html?itemId=97409 - Ignite Basic
04. http://204.14.53.152/viewQueued.html?itemId=97410 - Ignite Cache
05. http://204.14.53.152/viewQueued.html?itemId=97411 - Ignite Cache 2
06. http://204.14.53.152/viewQueued.html?itemId=97412 - Ignite Cache 3
07. http://204.14.53.152/viewQueued.html?itemId=97413 - Ignite Cache 4
08. http://204.14.53.152/viewQueued.html?itemId=97414 - Ignite Cache Expiry
Policy
09. http://204.14.53.152/viewQueued.html?itemId=97415 - Ignite Cache Failover
10. http://204.14.53.152/viewQueued.html?itemId=97416 - Ignite Cache Failover
Multi JVM
11. http://204.14.53.152/viewQueued.html?itemId=97417 - Ignite Cache Failover2
12. http://204.14.53.152/viewQueued.html?itemId=97418 - Ignite Cache Full API
13. http://204.14.53.152/viewQueued.html?itemId=97419 - Ignite Cache Full API
Multi JVM
14. http://204.14.53.152/viewQueued.html?itemId=97420 - Ignite Cache Restarts
15. http://204.14.53.152/viewQueued.html?itemId=97421 - Ignite Cache Tx Recovery
16. http://204.14.53.152/viewQueued.html?itemId=97422 - Ignite Cloud
17. http://204.14.53.152/viewQueued.html?itemId=97423 - Ignite Compute Grid
18. http://204.14.53.152/viewQueued.html?itemId=97424 - Ignite Data Strucutures
19. http://204.14.53.152/viewQueued.html?itemId=97425 - Ignite Examples
20. http://204.14.53.152/viewQueued.html?itemId=97426 - Ignite GCE
21. http://204.14.53.152/viewQueued.html?itemId=97427 - Ignite Geospacial
Indexing
22. http://204.14.53.152/viewQueued.html?itemId=97428 - Ignite H2 Indexing
23. http://204.14.53.152/viewQueued.html?itemId=97429 - Ignite Hadoop
24. http://204.14.53.152/viewQueued.html?itemId=97430 - Ignite Hibernate
25. http://204.14.53.152/viewQueued.html?itemId=97431 - Ignite IGFS
26. http://204.14.53.152/viewQueued.html?itemId=97432 - Ignite IGFS Examples
27. http://204.14.53.152/viewQueued.html?itemId=97433 - Ignite IGFS Linux and
MacOS
28. http://204.14.53.152/viewQueued.html?itemId=97434 - Ignite Java Client
29. http://204.14.53.152/viewQueued.html?itemId=97435 - Ignite JDBC Driver
30. http://204.14.53.152/viewQueued.html?itemId=97436 - Ignite JTA
31. http://204.14.53.152/viewQueued.html?itemId=97437 - Ignite Logging
32. http://204.14.53.152/viewQueued.html?itemId=97438 - Ignite Queries
33. http://204.14.53.152/viewQueued.html?itemId=97439 - Ignite Scalar Examples
34. http://204.14.53.152/viewQueued.html?itemId=97440 - Ignite SPI
35. http://204.14.53.152/viewQueued.html?itemId=97441 - Ignite Spring
36. http://204.14.53.152/viewQueued.html?itemId=97442 - Ignite Start Nodes
37. http://204.14.53.152/viewQueued.html?itemId=97443 - Ignite URI Deploy SPI
38. http://204.14.53.152/viewQueued.html?itemId=97444 - Ignite Visor Console
39. http://204.14.53.152/viewQueued.html?itemId=97445 - Ignite WebSessions
40. http://204.14.53.152/viewQueued.html?itemId=97446 - JCache TCK
> 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
>
> Attachments: master_ae11e9b_ignite-1228.patch
>
>
> 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)
