[
https://issues.apache.org/jira/browse/LOG4J2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377218#comment-14377218
]
Gary Gregory commented on LOG4J2-982:
-------------------------------------
Well, this is odd: With the v2 patch, when I run {{mvn test -pl !log4j-perf}}
the build seems to hang with the last output being:
{noformat}
...
2015-03-23 12:31:08,329 DEBUG PluginManager 'Converter' found 33 plugins
2015-03-23 12:31:08,335 DEBUG Jansi is not installed, cannot find
org.fusesource.jansi.WindowsAnsiOutputStream
2015-03-23 12:31:08,411 DEBUG Starting configuration
org.apache.logging.log4j.core.config.DefaultConfiguration@24313fcc
2015-03-23 12:31:08,413 DEBUG PluginManager 'Core' found 78 plugins
2015-03-23 12:31:08,413 DEBUG PluginManager 'Level' found 1 plugins
2015-03-23 12:31:08,414 DEBUG Started configuration
org.apache.logging.log4j.core.config.DefaultConfiguration@24313fcc OK.
2015-03-23 12:31:08,426 DEBUG Shutting down FlumeEmbeddedManager
eventLogger-c8cfe1a5ff8d0d448513df48a3dd44f8
2015-03-23 12:31:08,549 DEBUG Stopped
XmlConfiguration[location=C:\vcs\git\apache\logging\logging-log4j2\log4j-flume-ng\target\test-classes\embedded.xml]
OK
2015-03-23 12:31:08,551 DEBUG Unregistering MBean
org.apache.logging.log4j2:type=1808253012
2015-03-23 12:31:08,553 DEBUG Unregistering MBean
org.apache.logging.log4j2:type=1808253012,component=StatusLogger
2015-03-23 12:31:08,554 DEBUG Unregistering MBean
org.apache.logging.log4j2:type=1808253012,component=ContextSelector
2015-03-23 12:31:08,556 DEBUG Unregistering MBean
org.apache.logging.log4j2:type=1808253012,component=Loggers,name=
2015-03-23 12:31:08,557 DEBUG Unregistering MBean
org.apache.logging.log4j2:type=1808253012,component=Loggers,name=EventLogger
2015-03-23 12:31:08,559 DEBUG Unregistering MBean
org.apache.logging.log4j2:type=1808253012,component=Appenders,name=eventLogger
2015-03-23 12:31:08,560 DEBUG Unregistering MBean
org.apache.logging.log4j2:type=1808253012,component=Appenders,name=STDOUT
2015-03-23 12:31:08,562 DEBUG Registering MBean
org.apache.logging.log4j2:type=1808253012
2015-03-23 12:31:08,563 DEBUG Registering MBean
org.apache.logging.log4j2:type=1808253012,component=StatusLogger
2015-03-23 12:31:08,567 DEBUG Registering MBean
org.apache.logging.log4j2:type=1808253012,component=ContextSelector
2015-03-23 12:31:08,568 DEBUG Registering MBean
org.apache.logging.log4j2:type=1808253012,component=Appenders,name=Console
2015-03-23 12:31:08,569 DEBUG Reconfiguration complete for
context[name=1808253012] at null
(org.apache.logging.log4j.core.LoggerContext@7dc36524) with optional
ClassLoader: null
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.298 sec - in
org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest
No Event returned
2015-03-23 12:31:15,474 ERROR No log4j2 configuration file found. Using default
configuration: logging only errors to the console.
2015-03-23 12:31:15,481 INFO Log4j appears to be running in a Servlet
environment, but there's no log4j-web module available. If you want better web
container support, please add the log4j-web JAR to your web archive or server
lib directory.
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.608 sec - in
org.apache.logging.log4j.flume.appender.FlumeAppenderTest
{noformat}
I killed the build after starting it over an hour ago.
I am running with:
{noformat}
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T13:10:27-07:00)
Maven home: C:\Java\apache-maven-3.3.1
Java version: 1.8.0_31, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_31\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
{noformat}
> Use System.nanoTime() to measure time intervals
> -----------------------------------------------
>
> Key: LOG4J2-982
> URL: https://issues.apache.org/jira/browse/LOG4J2-982
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core, Flume Appender
> Reporter: Mikhail Mazurskiy
> Priority: Minor
> Attachments: LOG4J2-982-v2.patch, LOG4J2-982.patch
>
>
> Unlike {{System.currentTimeMillis()}}, which can jump/slew forward and
> backwards, {{System.nanoTime()}} is a monotonic clock (at least it should be)
> and hence it should be used to measure time intervals (timeouts/delays/etc).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
