Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #18

[Apache Jenkins Server]

See 


--
[...truncated 16055 lines...]
2017-02-13 07:21:58,777 main DEBUG Starting OutputStreamManager 
SYSTEM_OUT.false.false
2017-02-13 07:21:58,777 main DEBUG Building Plugin[name=layout, 
class=org.apache.logging.log4j.core.layout.PatternLayout].
2017-02-13 07:21:58,778 main DEBUG PatternLayout$Builder(pattern="%d %p %C{1.} 
[%t] %m%n", PatternSelector=null, Configuration(PropertiesConfigTest), 
Replace=null, charset="null", alwaysWriteExceptions="null", disableAnsi="null", 
noConsoleNoAnsi="null", header="null", footer="null")
2017-02-13 07:21:58,811 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.FileAppender].
2017-02-13 07:21:58,817 main DEBUG 
FileAppender$Builder(fileName="target/test-properties.log", append="null", 
locking="null", advertise="null", advertiseUri="null", createOnDemand="null", 
bufferedIo="false", bufferSize="null", immediateFlush="null", 
ignoreExceptions="null", PatternLayout(%d %p %C{1.} [%t] %m%n), name="File", 
Configuration(PropertiesConfigTest), Filter=null)
2017-02-13 07:21:58,818 main WARN The bufferSize is set to 8192 but bufferedIo 
is false: false
2017-02-13 07:21:58,822 main DEBUG Starting FileManager 
target/test-properties.log
2017-02-13 07:21:58,822 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-02-13 07:21:58,825 main DEBUG createFilter(level="ERROR", onMatch="null", 
onMismatch="null")
2017-02-13 07:21:58,825 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.test.appender.ListAppender].
2017-02-13 07:21:58,828 main DEBUG ListAppender$Builder(name="List", 
entryPerNewLine="null", raw="null", Layout=null, ThresholdFilter(ERROR))
2017-02-13 07:21:58,828 main DEBUG Building Plugin[name=appenders, 
class=org.apache.logging.log4j.core.config.AppendersPlugin].
2017-02-13 07:21:58,829 main DEBUG createAppenders(={STDOUT, File, List})
2017-02-13 07:21:58,829 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-02-13 07:21:58,830 main DEBUG createFilter(level="DEBUG", onMatch="null", 
onMismatch="null")
2017-02-13 07:21:58,831 main DEBUG Configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
 initialized
2017-02-13 07:21:58,831 main DEBUG Starting configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
2017-02-13 07:21:58,833 main DEBUG Log4j2 ConfigurationScheduler starting 1 
threads
2017-02-13 07:21:58,834 main DEBUG Started configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
 OK.
2017-02-13 07:21:58,836 main DEBUG Shutting down OutputStreamManager 
SYSTEM_OUT.false.false-1
2017-02-13 07:21:58,837 main DEBUG Shut down OutputStreamManager 
SYSTEM_OUT.false.false-1, all resources released: true
2017-02-13 07:21:58,837 main DEBUG Appender DefaultConsole-1 stopped with 
status true
2017-02-13 07:21:58,838 main DEBUG Stopped 
org.apache.logging.log4j.core.config.DefaultConfiguration@7921b0a2 OK
2017-02-13 07:21:58,963 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest
2017-02-13 07:21:58,970 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=StatusLogger
2017-02-13 07:21:58,973 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=ContextSelector
2017-02-13 07:21:58,977 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=org.apache.logging.log4j.test1
2017-02-13 07:21:58,979 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=
2017-02-13 07:21:58,979 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=org.apache.logging.log4j.test2
2017-02-13 07:21:58,982 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Appenders,name=STDOUT
2017-02-13 07:21:58,982 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Appenders,name=List
2017-02-13 07:21:58,984 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Appenders,name=File
2017-02-13 07:21:58,986 main DEBUG 
LoggerContext[name=org.apache.logging.log4j.core.PropertiesFileConfigTest, 
org.apache.logging.log4j.core.LoggerContext@57fffcd7] started OK with 
configuration 

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #18

[Apache Jenkins Server]

See 


--
[...truncated 15999 lines...]
2017-02-13 07:20:05,280 main DEBUG Starting FileManager 
target/test-properties.log
2017-02-13 07:20:05,281 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-02-13 07:20:05,283 main DEBUG createFilter(level="ERROR", onMatch="null", 
onMismatch="null")
2017-02-13 07:20:05,283 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.test.appender.ListAppender].
2017-02-13 07:20:05,284 main DEBUG ListAppender$Builder(name="List", 
entryPerNewLine="null", raw="null", Layout=null, ThresholdFilter(ERROR))
2017-02-13 07:20:05,286 main DEBUG Building Plugin[name=layout, 
class=org.apache.logging.log4j.core.layout.PatternLayout].
2017-02-13 07:20:05,287 main DEBUG PatternLayout$Builder(pattern="%m%n", 
PatternSelector=null, Configuration(PropertiesConfigTest), Replace=null, 
charset="null", alwaysWriteExceptions="null", disableAnsi="null", 
noConsoleNoAnsi="null", header="null", footer="null")
2017-02-13 07:20:05,288 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.ConsoleAppender].
2017-02-13 07:20:05,291 main DEBUG ConsoleAppender$Builder(target="null", 
follow="null", direct="null", bufferedIo="null", bufferSize="null", 
immediateFlush="null", ignoreExceptions="null", PatternLayout(%m%n), 
name="STDOUT", Configuration(PropertiesConfigTest), Filter=null)
2017-02-13 07:20:05,291 main WARN Unable to instantiate 
org.fusesource.jansi.WindowsAnsiOutputStream
2017-02-13 07:20:05,292 main DEBUG Starting OutputStreamManager 
SYSTEM_OUT.false.false
2017-02-13 07:20:05,292 main DEBUG Building Plugin[name=appenders, 
class=org.apache.logging.log4j.core.config.AppendersPlugin].
2017-02-13 07:20:05,293 main DEBUG createAppenders(={File, List, STDOUT})
2017-02-13 07:20:05,293 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-02-13 07:20:05,294 main DEBUG createFilter(level="DEBUG", onMatch="null", 
onMismatch="null")
2017-02-13 07:20:05,295 main DEBUG Configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@2a08904c
 initialized
2017-02-13 07:20:05,296 main DEBUG Starting configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@2a08904c
2017-02-13 07:20:05,297 main DEBUG Log4j2 ConfigurationScheduler starting 1 
threads
2017-02-13 07:20:05,298 main DEBUG Started configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@2a08904c
 OK.
2017-02-13 07:20:05,299 main DEBUG Shutting down OutputStreamManager 
SYSTEM_OUT.false.false-1
2017-02-13 07:20:05,300 main DEBUG Shut down OutputStreamManager 
SYSTEM_OUT.false.false-1, all resources released: true
2017-02-13 07:20:05,300 main DEBUG Appender DefaultConsole-1 stopped with 
status true
2017-02-13 07:20:05,300 main DEBUG Stopped 
org.apache.logging.log4j.core.config.DefaultConfiguration@17616cae OK
2017-02-13 07:20:05,401 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest
2017-02-13 07:20:05,405 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=StatusLogger
2017-02-13 07:20:05,408 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=ContextSelector
2017-02-13 07:20:05,411 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=org.apache.logging.log4j.test2
2017-02-13 07:20:05,411 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=
2017-02-13 07:20:05,412 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=org.apache.logging.log4j.test1
2017-02-13 07:20:05,413 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Appenders,name=List
2017-02-13 07:20:05,415 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Appenders,name=STDOUT
2017-02-13 07:20:05,415 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Appenders,name=File
2017-02-13 07:20:05,418 main DEBUG 
LoggerContext[name=org.apache.logging.log4j.core.PropertiesFileConfigTest, 
org.apache.logging.log4j.core.LoggerContext@16cbfbed] started OK with 
configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@2a08904c.
Running 

Re: RollingAppenderSizeTest failures

[Matt Sicker]

Also, using a similar multi-config Jenkins job, we can set up JDK 7, 8, and
9pre Linux builds as well.

On 13 February 2017 at 01:08, Matt Sicker  wrote:

> Sorry for the deluge of build emails, forgot to disable that.
>
> Anyways, I got the build running for Windows:  job/Log4jWindows/>. I have it set to run daily for now as there's only
> two windows VMs and I don't want to hog them.
>
> Ok, I have no idea why the mvnw script isn't running on there properly,
> but I did manage to find the proper incantation to run mvn on that Windows
> VM. This project has examples:  job/infra-test-maven-windows/>.
>
> On 12 February 2017 at 23:10, Matt Sicker  wrote:
>
>> Well, I've got some sort of thing working across a rather unintentionally
>> wide variety of environments. Turns out getting the Windows builds to work
>> might be simplified by including a maven wrapper because I don't really
>> know how these VMs are set up.
>>
>> On 12 February 2017 at 22:52, Matt Sicker  wrote:
>>
>>> JAVA_HOME not defined correctly on almost all the environments. Well
>>> now...
>>>
>>> On 12 February 2017 at 22:50, Matt Sicker  wrote:
>>>
 I've set up a basic test matrix for Java 7 and 8 on Linux and Windows
 here: 

 Let's see how this works.

 On 12 February 2017 at 22:40, Matt Sicker  wrote:

> I'm not really sure how to go about fixing the tests, but I was
> thinking of setting up a Jenkins job for multi-environment testing to try
> and catch these issues sooner.
>
> On 12 February 2017 at 22:16, Gary Gregory 
> wrote:
>
>> Any chance building on Windows gets solved soon-ish?
>>
>> Gary
>>
>> On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory 
>> wrote:
>>
>>> Git bisec says:
>>>
>>> *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit*
>>> commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a
>>> Author: Ralph Goers 
>>> Date:   Tue Jan 24 14:48:34 2017 -0700
>>>
>>> Use an ExecutorService to verify shutdown of the async threads
>>>
>>> :04 04 ad3cb23efafeaab2f7e934e249c8e53ff7dcf86f
>>> 056bbb158f43602fb2a4e8c74c5bcff29e5e5fe5 M  log4j-core
>>> bisect run success
>>>
>>>
>>> I'm not sure what needs to be reverted or changed but there you have
>>> it (I have to get back to a customer issue now).
>>>
>>> If you want to do this yourself you can run:
>>>
>>> git bisect start HEAD log4j-2.7
>>>
>>> (I was not sure how far back to go so I picked 2.7. It turns out I
>>> could have used 2.8. Then in a script called ..\run.cmd I have:
>>>
>>> call mvn clean
>>> call mvn -DskipTests -pl log4j-api install
>>> mvn -Dtest=RollingAppenderSizeTest -pl log4j-core test
>>>
>>> and run:
>>>
>>> git bisect run ..\run.cmd
>>>
>>> which gives you the output at the start of this message.
>>>
>>> Gary
>>>
>>>
>>> On Thu, Feb 2, 2017 at 5:01 PM, Gary Gregory >> > wrote:
>>>
 I get:

 Tests in error:
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗
 FileSystem target\rolli...

 Tests run: 1879, Failures: 0, Errors: 10, Skipped: 30

 using:

 Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
 2015-11-10T08:41:47-08:00)
 Maven home: C:\Java\apache-maven-3.3.9\bin\..
 Java version: 1.7.0_80, vendor: Oracle Corporation
 Java home: C:\Program Files\Java\jdk1.7.0_80\jre
 Default locale: en_US, platform encoding: Cp1252
 OS name: "windows 8.1", version: "6.3", arch: "amd64", family:
 "windows"

 Anyone else?

 --
 

Re: RollingAppenderSizeTest failures

[Matt Sicker]

Sorry for the deluge of build emails, forgot to disable that.

Anyways, I got the build running for Windows: <
https://builds.apache.org/job/Log4jWindows/>. I have it set to run daily
for now as there's only two windows VMs and I don't want to hog them.

Ok, I have no idea why the mvnw script isn't running on there properly, but
I did manage to find the proper incantation to run mvn on that Windows VM.
This project has examples: <
https://builds.apache.org/job/infra-test-maven-windows/>.

On 12 February 2017 at 23:10, Matt Sicker  wrote:

> Well, I've got some sort of thing working across a rather unintentionally
> wide variety of environments. Turns out getting the Windows builds to work
> might be simplified by including a maven wrapper because I don't really
> know how these VMs are set up.
>
> On 12 February 2017 at 22:52, Matt Sicker  wrote:
>
>> JAVA_HOME not defined correctly on almost all the environments. Well
>> now...
>>
>> On 12 February 2017 at 22:50, Matt Sicker  wrote:
>>
>>> I've set up a basic test matrix for Java 7 and 8 on Linux and Windows
>>> here: 
>>>
>>> Let's see how this works.
>>>
>>> On 12 February 2017 at 22:40, Matt Sicker  wrote:
>>>
 I'm not really sure how to go about fixing the tests, but I was
 thinking of setting up a Jenkins job for multi-environment testing to try
 and catch these issues sooner.

 On 12 February 2017 at 22:16, Gary Gregory 
 wrote:

> Any chance building on Windows gets solved soon-ish?
>
> Gary
>
> On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory 
> wrote:
>
>> Git bisec says:
>>
>> *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit*
>> commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a
>> Author: Ralph Goers 
>> Date:   Tue Jan 24 14:48:34 2017 -0700
>>
>> Use an ExecutorService to verify shutdown of the async threads
>>
>> :04 04 ad3cb23efafeaab2f7e934e249c8e53ff7dcf86f
>> 056bbb158f43602fb2a4e8c74c5bcff29e5e5fe5 M  log4j-core
>> bisect run success
>>
>>
>> I'm not sure what needs to be reverted or changed but there you have
>> it (I have to get back to a customer issue now).
>>
>> If you want to do this yourself you can run:
>>
>> git bisect start HEAD log4j-2.7
>>
>> (I was not sure how far back to go so I picked 2.7. It turns out I
>> could have used 2.8. Then in a script called ..\run.cmd I have:
>>
>> call mvn clean
>> call mvn -DskipTests -pl log4j-api install
>> mvn -Dtest=RollingAppenderSizeTest -pl log4j-core test
>>
>> and run:
>>
>> git bisect run ..\run.cmd
>>
>> which gives you the output at the start of this message.
>>
>> Gary
>>
>>
>> On Thu, Feb 2, 2017 at 5:01 PM, Gary Gregory 
>> wrote:
>>
>>> I get:
>>>
>>> Tests in error:
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>
>>> Tests run: 1879, Failures: 0, Errors: 10, Skipped: 30
>>>
>>> using:
>>>
>>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>>> 2015-11-10T08:41:47-08:00)
>>> Maven home: C:\Java\apache-maven-3.3.9\bin\..
>>> Java version: 1.7.0_80, vendor: Oracle Corporation
>>> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 8.1", version: "6.3", arch: "amd64", family:
>>> "windows"
>>>
>>> Anyone else?
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> 
>>>
>>> 

Fwd: logging-log4j2 git commit: Try out specifying bash in mvnw to make Jenkins happy

[Matt Sicker]

Bug filed: https://github.com/takari/maven-wrapper/issues/34

-- Forwarded message --
From: 
Date: 12 February 2017 at 23:34
Subject: logging-log4j2 git commit: Try out specifying bash in mvnw to make
Jenkins happy
To: comm...@logging.apache.org


Repository: logging-log4j2
Updated Branches:
  refs/heads/master 3e1f9c7a5 -> 291c7101b


Try out specifying bash in mvnw to make Jenkins happy


Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/
commit/291c7101
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/291c7101
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/291c7101

Branch: refs/heads/master
Commit: 291c7101b3ec6715cef411043f16b906bef07cfb
Parents: 3e1f9c7
Author: Matt Sicker 
Authored: Sun Feb 12 23:33:43 2017 -0600
Committer: Matt Sicker 
Committed: Sun Feb 12 23:33:43 2017 -0600

--
 mvnw | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/291c7101/mvnw
--
diff --git a/mvnw b/mvnw
index 6ecc150..f5ef4d1 100755
--- a/mvnw
+++ b/mvnw
@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/bin/bash
 # 

 # Licensed to the Apache Software Foundation (ASF) under one
 # or more contributor license agreements.  See the NOTICE file

Jenkins build is back to normal : Log4jScala #19

[Apache Jenkins Server]

See 


-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.7 (unlimited security) 64-bit Windows only #6

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 6
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H18 (ubuntu) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 291c7101b3ec6715cef411043f16b906bef07cfb # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.7 (unlimited security) 64-bit Windows only] $ /bin/bash -xe 
/tmp/hudson4133535186724452425.sh
+ env
BUILD_URL=https://builds.apache.org/job/Log4j/jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only/6/
XDG_SESSION_ID=228
HUDSON_SERVER_COOKIE=f4ebd1e6b0d976e8
SHELL=/bin/bash
SSH_CLIENT=140.211.11.14 40780 22
BUILD_TAG=jenkins-Log4j-jdk=JDK 1.7 (unlimited security) 64-bit Windows only-6
GIT_PREVIOUS_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
ROOT_BUILD_CAUSE=MANUALTRIGGER
WORKSPACE=
JOB_URL=https://builds.apache.org/job/Log4j/jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only/
USER=jenkins
BUILD_CAUSE_UPSTREAMTRIGGER=true
GIT_AUTHOR_NAME=jenkins
GIT_COMMITTER_NAME=jenkins
NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
GIT_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
JENKINS_HOME=/x1/jenkins/jenkins-home
PATH=F:\\hudson\\tools\\java\\jdk1.7.0_79-unlimited-security/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
MAIL=/var/mail/jenkins
_=/usr/bin/env
GIT_COMMITTER_EMAIL=bui...@apache.org
PWD=
JAVA_HOME=F:\\hudson\\tools\\java\\jdk1.7.0_79-unlimited-security
HUDSON_URL=https://builds.apache.org/
LANG=en_US.UTF-8
jdk=JDK 1.7 (unlimited security) 64-bit Windows only
JOB_NAME=Log4j/jdk=JDK 1.7 (unlimited security) 64-bit Windows only
BUILD_DISPLAY_NAME=#6
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
BUILD_CAUSE=UPSTREAMTRIGGER
BUILD_ID=6
JENKINS_URL=https://builds.apache.org/
JOB_BASE_NAME=jdk=JDK 1.7 (unlimited security) 64-bit Windows only
HOME=/home/jenkins
SHLVL=2
GIT_BRANCH=origin/master
JENKINS_SERVER_COOKIE=f4ebd1e6b0d976e8
EXECUTOR_NUMBER=0
GIT_URL=https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
NODE_LABELS=H18 ubuntu
LOGNAME=jenkins
SSH_CONNECTION=140.211.11.14 40780 67.195.81.138 22
HUDSON_HOME=/x1/jenkins/jenkins-home
NODE_NAME=H18
BUILD_NUMBER=6
XDG_RUNTIME_DIR=/run/user/10025
HUDSON_COOKIE=3f53302c-5979-4c9e-aadc-8b9bfcb88000
ROOT_BUILD_CAUSE_MANUALTRIGGER=true
GIT_AUTHOR_EMAIL=bui...@apache.org
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute 
F:\\hudson\\tools\\java\\jdk1.7.0_79-unlimited-security/bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » OpenJDK 8 (on Ubuntu only) #6

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 6
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H12 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 291c7101b3ec6715cef411043f16b906bef07cfb # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[OpenJDK 8 (on Ubuntu only) ] $ /bin/bash -xe /tmp/hudson2516453256914392564.sh
+ env
BUILD_URL=https://builds.apache.org/job/Log4j/jdk=OpenJDK%208%20(on%20Ubuntu%20only)%20/6/
XDG_SESSION_ID=154
HUDSON_SERVER_COOKIE=f4ebd1e6b0d976e8
SHELL=/bin/bash
SSH_CLIENT=140.211.11.14 55276 22
BUILD_TAG=jenkins-Log4j-jdk=OpenJDK 8 (on Ubuntu only) -6
GIT_PREVIOUS_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
ROOT_BUILD_CAUSE=MANUALTRIGGER
WORKSPACE=
JOB_URL=https://builds.apache.org/job/Log4j/jdk=OpenJDK%208%20(on%20Ubuntu%20only)%20/
USER=jenkins
BUILD_CAUSE_UPSTREAMTRIGGER=true
GIT_AUTHOR_NAME=jenkins
GIT_COMMITTER_NAME=jenkins
NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
GIT_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
JENKINS_HOME=/x1/jenkins/jenkins-home
PATH=/usr/lib/jvm/java-8-openjdk-amd64//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
MAIL=/var/mail/jenkins
_=/usr/bin/env
GIT_COMMITTER_EMAIL=bui...@apache.org
PWD=
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/
HUDSON_URL=https://builds.apache.org/
LANG=en_US.UTF-8
jdk=OpenJDK 8 (on Ubuntu only) 
JOB_NAME=Log4j/jdk=OpenJDK 8 (on Ubuntu only) 
BUILD_DISPLAY_NAME=#6
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
BUILD_CAUSE=UPSTREAMTRIGGER
BUILD_ID=6
JENKINS_URL=https://builds.apache.org/
JOB_BASE_NAME=jdk=OpenJDK 8 (on Ubuntu only) 
HOME=/home/jenkins
SHLVL=2
GIT_BRANCH=origin/master
JENKINS_SERVER_COOKIE=f4ebd1e6b0d976e8
EXECUTOR_NUMBER=1
GIT_URL=https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
NODE_LABELS=H12 Hadoop
LOGNAME=jenkins
SSH_CONNECTION=140.211.11.14 55276 67.195.81.156 22
HUDSON_HOME=/x1/jenkins/jenkins-home
NODE_NAME=H12
BUILD_NUMBER=6
XDG_RUNTIME_DIR=/run/user/10025
HUDSON_COOKIE=d64f8dd3-9eae-4cc3-9b5a-3fdd6ccdf95c
ROOT_BUILD_CAUSE_MANUALTRIGGER=true
GIT_AUTHOR_EMAIL=bui...@apache.org
+ ./mvnw
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.logging.log4j:log4j-slf4j-impl:jar:2.8.1-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate declaration of 
version (?) @ org.apache.logging.log4j:log4j-slf4j-impl:[unknown-version], 

 line 70, column 17
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.logging.log4j:log4j-jmx-gui:jar:2.8.1-SNAPSHOT
[WARNING] 'dependencies.dependency.systemPath' for com.sun:jconsole:jar refers 
to a non-existing file 
/usr/lib/jvm/java-8-openjdk-amd64/jre/../lib/jconsole.jar. Please verify that 
you run Maven using a JDK and not just a JRE. @ 
org.apache.logging.log4j:log4j-jmx-gui:[unknown-version], 

 line 199, column 23
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.logging.log4j:log4j-bom:pom:2.8.1-SNAPSHOT
[WARNING] 'parent.relativePath' of POM 
org.apache.logging.log4j:log4j-bom:2.8.1-SNAPSHOT 
(
 points at org.apache.logging.log4j:log4j instead of 
org.apache.logging:logging-parent, please verify your project structure @ line 
19, 

Build failed in Jenkins: Log4j » JDK 1.8 (unlimited security) 64-bit Windows only #6

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 6
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H10 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 291c7101b3ec6715cef411043f16b906bef07cfb # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.8 (unlimited security) 64-bit Windows only] $ /bin/bash -xe 
/tmp/hudson8836807329912565346.sh
+ env
BUILD_URL=https://builds.apache.org/job/Log4j/jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only/6/
XDG_SESSION_ID=149
HUDSON_SERVER_COOKIE=f4ebd1e6b0d976e8
SHELL=/bin/bash
SSH_CLIENT=140.211.11.14 54166 22
BUILD_TAG=jenkins-Log4j-jdk=JDK 1.8 (unlimited security) 64-bit Windows only-6
GIT_PREVIOUS_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
ROOT_BUILD_CAUSE=MANUALTRIGGER
WORKSPACE=
JOB_URL=https://builds.apache.org/job/Log4j/jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only/
USER=jenkins
BUILD_CAUSE_UPSTREAMTRIGGER=true
GIT_AUTHOR_NAME=jenkins
GIT_COMMITTER_NAME=jenkins
NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
GIT_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
JENKINS_HOME=/x1/jenkins/jenkins-home
PATH=F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
MAIL=/var/mail/jenkins
_=/usr/bin/env
GIT_COMMITTER_EMAIL=bui...@apache.org
PWD=
JAVA_HOME=F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security
HUDSON_URL=https://builds.apache.org/
LANG=en_US.UTF-8
jdk=JDK 1.8 (unlimited security) 64-bit Windows only
JOB_NAME=Log4j/jdk=JDK 1.8 (unlimited security) 64-bit Windows only
BUILD_DISPLAY_NAME=#6
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
BUILD_CAUSE=UPSTREAMTRIGGER
BUILD_ID=6
JENKINS_URL=https://builds.apache.org/
JOB_BASE_NAME=jdk=JDK 1.8 (unlimited security) 64-bit Windows only
HOME=/home/jenkins
SHLVL=2
GIT_BRANCH=origin/master
JENKINS_SERVER_COOKIE=f4ebd1e6b0d976e8
EXECUTOR_NUMBER=0
GIT_URL=https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
NODE_LABELS=H10 Hadoop
LOGNAME=jenkins
SSH_CONNECTION=140.211.11.14 54166 67.195.81.154 22
HUDSON_HOME=/x1/jenkins/jenkins-home
NODE_NAME=H10
BUILD_NUMBER=6
XDG_RUNTIME_DIR=/run/user/10021
HUDSON_COOKIE=845a53c3-0148-40df-b360-5ced9180ee88
ROOT_BUILD_CAUSE_MANUALTRIGGER=true
GIT_AUTHOR_EMAIL=bui...@apache.org
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute 
F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security/bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » OpenJDK 7 (on Ubuntu only) #6

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 6
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H13 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 291c7101b3ec6715cef411043f16b906bef07cfb # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[OpenJDK 7 (on Ubuntu only) ] $ /bin/bash -xe /tmp/hudson7673527319246842671.sh
+ env
BUILD_URL=https://builds.apache.org/job/Log4j/jdk=OpenJDK%207%20(on%20Ubuntu%20only)%20/6/
XDG_SESSION_ID=186
HUDSON_SERVER_COOKIE=f4ebd1e6b0d976e8
SHELL=/bin/bash
SSH_CLIENT=140.211.11.14 37121 22
BUILD_TAG=jenkins-Log4j-jdk=OpenJDK 7 (on Ubuntu only) -6
GIT_PREVIOUS_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
ROOT_BUILD_CAUSE=MANUALTRIGGER
WORKSPACE=
JOB_URL=https://builds.apache.org/job/Log4j/jdk=OpenJDK%207%20(on%20Ubuntu%20only)%20/
USER=jenkins
BUILD_CAUSE_UPSTREAMTRIGGER=true
GIT_AUTHOR_NAME=jenkins
GIT_COMMITTER_NAME=jenkins
NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
GIT_COMMIT=291c7101b3ec6715cef411043f16b906bef07cfb
JENKINS_HOME=/x1/jenkins/jenkins-home
PATH=/usr/lib/jvm/java-7-openjdk-amd64//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
MAIL=/var/mail/jenkins
_=/usr/bin/env
GIT_COMMITTER_EMAIL=bui...@apache.org
PWD=
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/
HUDSON_URL=https://builds.apache.org/
LANG=en_US.UTF-8
jdk=OpenJDK 7 (on Ubuntu only) 
JOB_NAME=Log4j/jdk=OpenJDK 7 (on Ubuntu only) 
BUILD_DISPLAY_NAME=#6
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
BUILD_CAUSE=UPSTREAMTRIGGER
BUILD_ID=6
JENKINS_URL=https://builds.apache.org/
JOB_BASE_NAME=jdk=OpenJDK 7 (on Ubuntu only) 
HOME=/home/jenkins
SHLVL=2
GIT_BRANCH=origin/master
JENKINS_SERVER_COOKIE=f4ebd1e6b0d976e8
EXECUTOR_NUMBER=0
GIT_URL=https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
NODE_LABELS=H13 Hadoop
LOGNAME=jenkins
SSH_CONNECTION=140.211.11.14 37121 67.195.81.157 22
HUDSON_HOME=/x1/jenkins/jenkins-home
NODE_NAME=H13
BUILD_NUMBER=6
XDG_RUNTIME_DIR=/run/user/10025
HUDSON_COOKIE=8b3e3358-3608-4ecf-9cc7-8c1178bf6213
ROOT_BUILD_CAUSE_MANUALTRIGGER=true
GIT_AUTHOR_EMAIL=bui...@apache.org
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » OpenJDK 8 (on Ubuntu only) #5

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Try out specifying bash in mvnw to make Jenkins happy

--
Started by upstream project "Log4j" build number 5
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H12 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 3e1f9c7a50e39b0de9d668d121be91f99d94704c # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[OpenJDK 8 (on Ubuntu only) ] $ /bin/bash -xe /tmp/hudson3970335307258678252.sh
+ ./mvnw
Downloading 
https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.zip
..
Unzipping 
/home/jenkins/.m2/wrapper/dists/apache-maven-3.3.9-bin/2609u9g41na2l7ogackmif6fj2/apache-maven-3.3.9-bin.zip
 to 
/home/jenkins/.m2/wrapper/dists/apache-maven-3.3.9-bin/2609u9g41na2l7ogackmif6fj2
Set executable permissions for: 
/home/jenkins/.m2/wrapper/dists/apache-maven-3.3.9-bin/2609u9g41na2l7ogackmif6fj2/apache-maven-3.3.9/bin/mvn
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.logging.log4j:log4j-slf4j-impl:jar:2.8.1-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate declaration of 
version (?) @ org.apache.logging.log4j:log4j-slf4j-impl:[unknown-version], 

 line 70, column 17
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.logging.log4j:log4j-jmx-gui:jar:2.8.1-SNAPSHOT
[WARNING] 'dependencies.dependency.systemPath' for com.sun:jconsole:jar refers 
to a non-existing file 
/usr/lib/jvm/java-8-openjdk-amd64/jre/../lib/jconsole.jar. Please verify that 
you run Maven using a JDK and not just a JRE. @ 
org.apache.logging.log4j:log4j-jmx-gui:[unknown-version], 

 line 199, column 23
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.logging.log4j:log4j-bom:pom:2.8.1-SNAPSHOT
[WARNING] 'parent.relativePath' of POM 
org.apache.logging.log4j:log4j-bom:2.8.1-SNAPSHOT 
(
 points at org.apache.logging.log4j:log4j instead of 
org.apache.logging:logging-parent, please verify your project structure @ line 
19, column 11
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Apache Log4j 2
[INFO] Apache Log4j API
[INFO] Apache Log4j Core
[INFO] Apache Log4j 1.x Compatibility API
[INFO] Apache Log4j SLF4J Binding
[INFO] Apache Log4j to SLF4J Adapter
[INFO] Apache Log4j Commons Logging Bridge
[INFO] Apache Log4j Flume Bridge
[INFO] Apache Log4j Web
[INFO] Apache Log4j Tag Library
[INFO] Apache Log4j JMX GUI
[INFO] Apache Log4j Samples
[INFO] Apache Log4j Samples: Flume - Common
[INFO] Apache Log4j Samples: Flume - Remote
[INFO] Apache Log4j Samples: Flume - Embedded
[INFO] Apache Log4j Samples: Configuration
[INFO] Apache Log4j 

Build failed in Jenkins: Log4j » OpenJDK 7 (on Ubuntu only) #5

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Try out specifying bash in mvnw to make Jenkins happy

--
Started by upstream project "Log4j" build number 5
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H13 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 3e1f9c7a50e39b0de9d668d121be91f99d94704c # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[OpenJDK 7 (on Ubuntu only) ] $ /bin/bash -xe /tmp/hudson83761371197985802.sh
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.8 (unlimited security) 64-bit Windows only #5

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Try out specifying bash in mvnw to make Jenkins happy

--
Started by upstream project "Log4j" build number 5
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H10 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 3e1f9c7a50e39b0de9d668d121be91f99d94704c # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.8 (unlimited security) 64-bit Windows only] $ /bin/bash -xe 
/tmp/hudson8428670815732789156.sh
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute 
F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security/bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.7 (unlimited security) 64-bit Windows only #5

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Try out specifying bash in mvnw to make Jenkins happy

--
Started by upstream project "Log4j" build number 5
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H18 (ubuntu) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 291c7101b3ec6715cef411043f16b906bef07cfb 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 291c7101b3ec6715cef411043f16b906bef07cfb
 > git rev-list 3e1f9c7a50e39b0de9d668d121be91f99d94704c # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.7 (unlimited security) 64-bit Windows only] $ /bin/bash -xe 
/tmp/hudson7876456079477662986.sh
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute 
F:\\hudson\\tools\\java\\jdk1.7.0_79-unlimited-security/bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.8 (unlimited security) 64-bit Windows only #4

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Add maven wrapper script

--
Started by upstream project "Log4j" build number 4
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H10 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 3e1f9c7a50e39b0de9d668d121be91f99d94704c 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3e1f9c7a50e39b0de9d668d121be91f99d94704c
 > git rev-list c826beb94de6912c3bbaa09726235d85aebd5bf5 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.8 (unlimited security) 64-bit Windows only] $ /bin/bash -xe 
/tmp/hudson8346688402993076115.sh
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute F:\hudson\tools\java\jdk1.8.0_92-unlimited-security/bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.7 (unlimited security) 64-bit Windows only #4

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Add maven wrapper script

--
Started by upstream project "Log4j" build number 4
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H18 (ubuntu) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 3e1f9c7a50e39b0de9d668d121be91f99d94704c 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3e1f9c7a50e39b0de9d668d121be91f99d94704c
 > git rev-list c826beb94de6912c3bbaa09726235d85aebd5bf5 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.7 (unlimited security) 64-bit Windows only] $ /bin/bash -xe 
/tmp/hudson7083303659786591503.sh
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute F:\hudson\tools\java\jdk1.7.0_79-unlimited-security/bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » OpenJDK 7 (on Ubuntu only) #4

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Add maven wrapper script

--
Started by upstream project "Log4j" build number 4
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H13 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 3e1f9c7a50e39b0de9d668d121be91f99d94704c 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3e1f9c7a50e39b0de9d668d121be91f99d94704c
 > git rev-list c826beb94de6912c3bbaa09726235d85aebd5bf5 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[OpenJDK 7 (on Ubuntu only) ] $ /bin/bash -xe /tmp/hudson3619377518605460924.sh
+ ./mvnw
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » OpenJDK 8 (on Ubuntu only) #4

[Apache Jenkins Server]

See 


Changes:

[Matt Sicker] Add maven wrapper script

--
Started by upstream project "Log4j" build number 4
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H12 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 3e1f9c7a50e39b0de9d668d121be91f99d94704c 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3e1f9c7a50e39b0de9d668d121be91f99d94704c
 > git rev-list c826beb94de6912c3bbaa09726235d85aebd5bf5 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[OpenJDK 8 (on Ubuntu only) ] $ /bin/bash -xe /tmp/hudson8046477964002787266.sh
+ ./mvnw
./mvnw: 190: local: 8: bad variable name
Error: Could not find or load main class 
org.apache.maven.wrapper.MavenWrapperMain
Build step 'Execute shell' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.8 (unlimited security) 64-bit Windows only #3

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 3
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H10 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
 > git rev-list c826beb94de6912c3bbaa09726235d85aebd5bf5 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.8 (unlimited security) 64-bit Windows only] $ 
/home/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn "-Djdk=JDK 1.8 (unlimited 
security) 64-bit Windows only" clean install
Error: JAVA_HOME is not defined correctly.
  We cannot execute F:\hudson\tools\java\jdk1.8.0_92-unlimited-security/bin/java
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » OpenJDK 8 (on Ubuntu only) #3

[Apache Jenkins Server]

See 


--
[...truncated 608 lines...]
544/564 KB   640/1332 KB   
544/564 KB   644/1332 KB   
544/564 KB   648/1332 KB   
548/564 KB   648/1332 KB   
552/564 KB   648/1332 KB   
556/564 KB   648/1332 KB   
560/564 KB   648/1332 KB   
560/564 KB   652/1332 KB   
560/564 KB   656/1332 KB   
564/564 KB   656/1332 KB   
564/564 KB   660/1332 KB   
564/564 KB   660/1332 KB   
564/564 KB   664/1332 KB   
564/564 KB   668/1332 KB   
564/564 KB   672/1332 KB   
564/564 KB   676/1332 KB   
564/564 KB   680/1332 KB   
564/564 KB   684/1332 KB   
564/564 KB   688/1332 KB   
564/564 KB   692/1332 KB   
564/564 KB   696/1332 KB   
564/564 KB   700/1332 KB   
564/564 KB   704/1332 KB   
564/564 KB   708/1332 KB   
564/564 KB   712/1332 KB   
564/564 KB   716/1332 KB   
564/564 KB   720/1332 KB   
564/564 KB   724/1332 KB   
564/564 KB   728/1332 KB   
564/564 KB   732/1332 KB   
564/564 KB   736/1332 KB   
564/564 KB   740/1332 KB   
564/564 KB   744/1332 KB   
564/564 KB   748/1332 KB   
564/564 KB   752/1332 KB   
564/564 KB   756/1332 KB   
564/564 KB   760/1332 KB   
564/564 KB   764/1332 KB   
564/564 KB   768/1332 KB   
564/564 KB   772/1332 KB   
564/564 KB   776/1332 KB   
564/564 KB   780/1332 KB   
564/564 KB   784/1332 KB   
564/564 KB   788/1332 KB   
564/564 KB   792/1332 KB   
564/564 KB   796/1332 KB   
564/564 KB   800/1332 KB   
564/564 KB   804/1332 KB   
564/564 KB   808/1332 KB   
564/564 KB   812/1332 KB   
564/564 KB   816/1332 KB   
564/564 KB   820/1332 KB   
564/564 KB   824/1332 KB   
   
Downloaded: 
https://repo.maven.apache.org/maven2/org/apache/felix/org.apache.felix.framework/4.6.1/org.apache.felix.framework-4.6.1.jar
 (564 KB at 4621.2 KB/sec)
828/1332 KB
832/1332 KB   
836/1332 KB   
840/1332 KB   
844/1332 KB   
848/1332 KB   
852/1332 KB   
856/1332 KB   
860/1332 KB   
864/1332 KB   
868/1332 KB   
872/1332 KB   
876/1332 KB   
880/1332 KB   
884/1332 KB   
888/1332 KB   
892/1332 KB   
896/1332 KB   
900/1332 KB   
904/1332 KB   
908/1332 KB   
912/1332 KB   
916/1332 KB   
920/1332 KB   
924/1332 KB   
928/1332 KB   
932/1332 KB   
936/1332 KB   
940/1332 KB   
944/1332 KB   
948/1332 KB   
952/1332 KB   
956/1332 KB   
960/1332 KB   
964/1332 KB   
968/1332 KB   
972/1332 KB   
976/1332 KB   
980/1332 KB   
984/1332 KB   
988/1332 KB   
992/1332 KB   
996/1332 KB   
1000/1332 KB   
1004/1332 KB   
1008/1332 KB   
1012/1332 KB   
1016/1332 KB   
1020/1332 KB   
1024/1332 KB   
1028/1332 KB   
1032/1332 KB   
1036/1332 KB   
1040/1332 KB   
1044/1332 KB   
1048/1332 KB   
1052/1332 KB   
1056/1332 KB   
1060/1332 KB   
1064/1332 KB   
1068/1332 KB   
1072/1332 KB   
1076/1332 KB   
1080/1332 KB   
1084/1332 KB   
1088/1332 KB   
1092/1332 KB   
1096/1332 KB   
1100/1332 KB   
1104/1332 KB   
1108/1332 KB   
1112/1332 KB   
1116/1332 KB   
1120/1332 KB   
1124/1332 KB   
1128/1332 KB   
1132/1332 KB   
1136/1332 KB   
1140/1332 KB   
1144/1332 KB   
1148/1332 KB   
1152/1332 KB   
1156/1332 KB   
1160/1332 KB   
1164/1332 KB   
1168/1332 KB   
1172/1332 KB   
1176/1332 KB   
1180/1332 KB   
1184/1332 KB   
1188/1332 KB   
1192/1332 KB   
1196/1332 KB   
1200/1332 KB   
1204/1332 KB   
1208/1332 KB   
1212/1332 KB   
1216/1332 KB   
1220/1332 KB   
1224/1332 KB   
1228/1332 KB   
1232/1332 KB   
1236/1332 KB   
1240/1332 KB   
1244/1332 KB   
1248/1332 KB   
1252/1332 KB   
1256/1332 KB   
1260/1332 KB   
1264/1332 KB   
1268/1332 KB   
1272/1332 KB   
1276/1332 KB   
1280/1332 KB   
1284/1332 KB   
1288/1332 KB   
1292/1332 KB   
1296/1332 KB   
1300/1332 KB   
1304/1332 KB   
1308/1332 KB   
1312/1332 KB   
1316/1332 KB   
1320/1332 KB   
1324/1332 KB   
1328/1332 KB   
1332/1332 KB   
   
Downloaded: 
https://repo.maven.apache.org/maven2/org/eclipse/osgi/org.eclipse.osgi/3.7.1/org.eclipse.osgi-3.7.1.jar
 (1332 KB at 8321.9 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ log4j-api ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ log4j-api ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ log4j-api ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ 
log4j-api ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @ log4j-api ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 114 source files to 

[WARNING] Unable to autodetect 'javac' path, using 'javac' from the 

Build failed in Jenkins: Log4j » JDK 1.7 (unlimited security) 64-bit Windows only #3

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 3
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H18 (ubuntu) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
 > git rev-list c826beb94de6912c3bbaa09726235d85aebd5bf5 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.7 (unlimited security) 64-bit Windows only] $ 
/home/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn "-Djdk=JDK 1.7 (unlimited 
security) 64-bit Windows only" clean install
Error: JAVA_HOME is not defined correctly.
  We cannot execute F:\hudson\tools\java\jdk1.7.0_79-unlimited-security/bin/java
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » OpenJDK 7 (on Ubuntu only) #3

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 3
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H13 (Hadoop) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[OpenJDK 7 (on Ubuntu only) ] $ 
/home/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn "-Djdk=OpenJDK 7 (on 
Ubuntu only) " clean install
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: RollingAppenderSizeTest failures

[Matt Sicker]

Well, I've got some sort of thing working across a rather unintentionally
wide variety of environments. Turns out getting the Windows builds to work
might be simplified by including a maven wrapper because I don't really
know how these VMs are set up.

On 12 February 2017 at 22:52, Matt Sicker  wrote:

> JAVA_HOME not defined correctly on almost all the environments. Well now...
>
> On 12 February 2017 at 22:50, Matt Sicker  wrote:
>
>> I've set up a basic test matrix for Java 7 and 8 on Linux and Windows
>> here: 
>>
>> Let's see how this works.
>>
>> On 12 February 2017 at 22:40, Matt Sicker  wrote:
>>
>>> I'm not really sure how to go about fixing the tests, but I was thinking
>>> of setting up a Jenkins job for multi-environment testing to try and catch
>>> these issues sooner.
>>>
>>> On 12 February 2017 at 22:16, Gary Gregory 
>>> wrote:
>>>
 Any chance building on Windows gets solved soon-ish?

 Gary

 On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory 
 wrote:

> Git bisec says:
>
> *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit*
> commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a
> Author: Ralph Goers 
> Date:   Tue Jan 24 14:48:34 2017 -0700
>
> Use an ExecutorService to verify shutdown of the async threads
>
> :04 04 ad3cb23efafeaab2f7e934e249c8e53ff7dcf86f
> 056bbb158f43602fb2a4e8c74c5bcff29e5e5fe5 M  log4j-core
> bisect run success
>
>
> I'm not sure what needs to be reverted or changed but there you have
> it (I have to get back to a customer issue now).
>
> If you want to do this yourself you can run:
>
> git bisect start HEAD log4j-2.7
>
> (I was not sure how far back to go so I picked 2.7. It turns out I
> could have used 2.8. Then in a script called ..\run.cmd I have:
>
> call mvn clean
> call mvn -DskipTests -pl log4j-api install
> mvn -Dtest=RollingAppenderSizeTest -pl log4j-core test
>
> and run:
>
> git bisect run ..\run.cmd
>
> which gives you the output at the start of this message.
>
> Gary
>
>
> On Thu, Feb 2, 2017 at 5:01 PM, Gary Gregory 
> wrote:
>
>> I get:
>>
>> Tests in error:
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>
>> Tests run: 1879, Failures: 0, Errors: 10, Skipped: 30
>>
>> using:
>>
>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> 2015-11-10T08:41:47-08:00)
>> Maven home: C:\Java\apache-maven-3.3.9\bin\..
>> Java version: 1.7.0_80, vendor: Oracle Corporation
>> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 8.1", version: "6.3", arch: "amd64", family:
>> "windows"
>>
>> Anyone else?
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 
>>
>> 
>> Spring Batch in Action
>> 
>> 
>> Blog: http://garygregory.wordpress.com
>> Home: 

Build failed in Jenkins: Log4j » windows-2012-2,JDK 1.7 (latest) #2

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 2
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windows) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
FATAL: Couldn’t find any executable in 
/home/jenkins/tools/maven/apache-maven-3.3.9
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » windows-2012-1,JDK 1.7 (latest) #2

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 2
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-1 (Windows) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
FATAL: Couldn’t find any executable in 
/home/jenkins/tools/maven/apache-maven-3.3.9
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: RollingAppenderSizeTest failures

[Matt Sicker]

JAVA_HOME not defined correctly on almost all the environments. Well now...

On 12 February 2017 at 22:50, Matt Sicker  wrote:

> I've set up a basic test matrix for Java 7 and 8 on Linux and Windows
> here: 
>
> Let's see how this works.
>
> On 12 February 2017 at 22:40, Matt Sicker  wrote:
>
>> I'm not really sure how to go about fixing the tests, but I was thinking
>> of setting up a Jenkins job for multi-environment testing to try and catch
>> these issues sooner.
>>
>> On 12 February 2017 at 22:16, Gary Gregory 
>> wrote:
>>
>>> Any chance building on Windows gets solved soon-ish?
>>>
>>> Gary
>>>
>>> On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory 
>>> wrote:
>>>
 Git bisec says:

 *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit*
 commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a
 Author: Ralph Goers 
 Date:   Tue Jan 24 14:48:34 2017 -0700

 Use an ExecutorService to verify shutdown of the async threads

 :04 04 ad3cb23efafeaab2f7e934e249c8e53ff7dcf86f
 056bbb158f43602fb2a4e8c74c5bcff29e5e5fe5 M  log4j-core
 bisect run success


 I'm not sure what needs to be reverted or changed but there you have it
 (I have to get back to a customer issue now).

 If you want to do this yourself you can run:

 git bisect start HEAD log4j-2.7

 (I was not sure how far back to go so I picked 2.7. It turns out I
 could have used 2.8. Then in a script called ..\run.cmd I have:

 call mvn clean
 call mvn -DskipTests -pl log4j-api install
 mvn -Dtest=RollingAppenderSizeTest -pl log4j-core test

 and run:

 git bisect run ..\run.cmd

 which gives you the output at the start of this message.

 Gary


 On Thu, Feb 2, 2017 at 5:01 PM, Gary Gregory 
 wrote:

> I get:
>
> Tests in error:
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
> target\rolli...
>
> Tests run: 1879, Failures: 0, Errors: 10, Skipped: 30
>
> using:
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T08:41:47-08:00)
> Maven home: C:\Java\apache-maven-3.3.9\bin\..
> Java version: 1.7.0_80, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family:
> "windows"
>
> Anyone else?
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
>
> 
> JUnit in Action, Second Edition
> 
>
> 
> Spring Batch in Action
> 
> 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 Java Persistence with Hibernate, Second Edition
 

 
 JUnit in 

Re: RollingAppenderSizeTest failures

[Matt Sicker]

I've set up a basic test matrix for Java 7 and 8 on Linux and Windows here:


Let's see how this works.

On 12 February 2017 at 22:40, Matt Sicker  wrote:

> I'm not really sure how to go about fixing the tests, but I was thinking
> of setting up a Jenkins job for multi-environment testing to try and catch
> these issues sooner.
>
> On 12 February 2017 at 22:16, Gary Gregory  wrote:
>
>> Any chance building on Windows gets solved soon-ish?
>>
>> Gary
>>
>> On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory 
>> wrote:
>>
>>> Git bisec says:
>>>
>>> *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit*
>>> commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a
>>> Author: Ralph Goers 
>>> Date:   Tue Jan 24 14:48:34 2017 -0700
>>>
>>> Use an ExecutorService to verify shutdown of the async threads
>>>
>>> :04 04 ad3cb23efafeaab2f7e934e249c8e53ff7dcf86f
>>> 056bbb158f43602fb2a4e8c74c5bcff29e5e5fe5 M  log4j-core
>>> bisect run success
>>>
>>>
>>> I'm not sure what needs to be reverted or changed but there you have it
>>> (I have to get back to a customer issue now).
>>>
>>> If you want to do this yourself you can run:
>>>
>>> git bisect start HEAD log4j-2.7
>>>
>>> (I was not sure how far back to go so I picked 2.7. It turns out I could
>>> have used 2.8. Then in a script called ..\run.cmd I have:
>>>
>>> call mvn clean
>>> call mvn -DskipTests -pl log4j-api install
>>> mvn -Dtest=RollingAppenderSizeTest -pl log4j-core test
>>>
>>> and run:
>>>
>>> git bisect run ..\run.cmd
>>>
>>> which gives you the output at the start of this message.
>>>
>>> Gary
>>>
>>>
>>> On Thu, Feb 2, 2017 at 5:01 PM, Gary Gregory 
>>> wrote:
>>>
 I get:

 Tests in error:
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...
   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
 target\rolli...

 Tests run: 1879, Failures: 0, Errors: 10, Skipped: 30

 using:

 Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
 2015-11-10T08:41:47-08:00)
 Maven home: C:\Java\apache-maven-3.3.9\bin\..
 Java version: 1.7.0_80, vendor: Oracle Corporation
 Java home: C:\Program Files\Java\jdk1.7.0_80\jre
 Default locale: en_US, platform encoding: Cp1252
 OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"

 Anyone else?

 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 Java Persistence with Hibernate, Second Edition
 

 
 JUnit in Action, Second Edition
 

 
 Spring Batch in Action
 
 
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory

>>>
>>>
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> 
>>>
>>> 
>>> JUnit in Action, Second Edition
>>> 
>>>
>>> 
>>> Spring Batch in Action
>>> 

Build failed in Jenkins: Log4j » JDK 1.8 (unlimited security) 64-bit Windows only #1

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 1
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H10 (Hadoop) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.8 (unlimited security) 64-bit Windows only] $ 
/home/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn "-Djdk=JDK 1.8 (unlimited 
security) 64-bit Windows only" clean install
Error: JAVA_HOME is not defined correctly.
  We cannot execute F:\hudson\tools\java\jdk1.8.0_92-unlimited-security/bin/java
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.7 (unlimited security) 64-bit Windows only #1

[Apache Jenkins Server]

See 


--
Started by upstream project "Log4j" build number 1
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H18 (ubuntu) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.7 (unlimited security) 64-bit Windows only] $ 
/home/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn "-Djdk=JDK 1.7 (unlimited 
security) 64-bit Windows only" clean install
Error: JAVA_HOME is not defined correctly.
  We cannot execute F:\hudson\tools\java\jdk1.7.0_79-unlimited-security/bin/java
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j » JDK 1.8 (latest) #1

[Apache Jenkins Server]

See 

--
Started by upstream project "Log4j" build number 1
originally caused by:
 Started by user Matt Sicker
[EnvInject] - Loading node environment variables.
Building remotely on H11 (Hadoop) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git init  
 > # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision c826beb94de6912c3bbaa09726235d85aebd5bf5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c826beb94de6912c3bbaa09726235d85aebd5bf5
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
[JDK 1.8 (latest)] $ /home/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn 
"-Djdk=JDK 1.8 (latest)" clean install
Error: JAVA_HOME is not defined correctly.
  We cannot execute /home/jenkins/tools/java/latest1.8/bin/java
Build step 'Invoke top-level Maven targets' marked build as failure

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: RollingAppenderSizeTest failures

[Matt Sicker]

I'm not really sure how to go about fixing the tests, but I was thinking of
setting up a Jenkins job for multi-environment testing to try and catch
these issues sooner.

On 12 February 2017 at 22:16, Gary Gregory  wrote:

> Any chance building on Windows gets solved soon-ish?
>
> Gary
>
> On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory 
> wrote:
>
>> Git bisec says:
>>
>> *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit*
>> commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a
>> Author: Ralph Goers 
>> Date:   Tue Jan 24 14:48:34 2017 -0700
>>
>> Use an ExecutorService to verify shutdown of the async threads
>>
>> :04 04 ad3cb23efafeaab2f7e934e249c8e53ff7dcf86f
>> 056bbb158f43602fb2a4e8c74c5bcff29e5e5fe5 M  log4j-core
>> bisect run success
>>
>>
>> I'm not sure what needs to be reverted or changed but there you have it
>> (I have to get back to a customer issue now).
>>
>> If you want to do this yourself you can run:
>>
>> git bisect start HEAD log4j-2.7
>>
>> (I was not sure how far back to go so I picked 2.7. It turns out I could
>> have used 2.8. Then in a script called ..\run.cmd I have:
>>
>> call mvn clean
>> call mvn -DskipTests -pl log4j-api install
>> mvn -Dtest=RollingAppenderSizeTest -pl log4j-core test
>>
>> and run:
>>
>> git bisect run ..\run.cmd
>>
>> which gives you the output at the start of this message.
>>
>> Gary
>>
>>
>> On Thu, Feb 2, 2017 at 5:01 PM, Gary Gregory 
>> wrote:
>>
>>> I get:
>>>
>>> Tests in error:
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>>> target\rolli...
>>>
>>> Tests run: 1879, Failures: 0, Errors: 10, Skipped: 30
>>>
>>> using:
>>>
>>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>>> 2015-11-10T08:41:47-08:00)
>>> Maven home: C:\Java\apache-maven-3.3.9\bin\..
>>> Java version: 1.7.0_80, vendor: Oracle Corporation
>>> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>>>
>>> Anyone else?
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> 
>>>
>>> 
>>> JUnit in Action, Second Edition
>>> 
>>>
>>> 
>>> Spring Batch in Action
>>> 
>>> 
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 
>>
>> 
>> Spring Batch in Action
>> 
>> 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! 

Re: RollingAppenderSizeTest failures

[Gary Gregory]

Any chance building on Windows gets solved soon-ish?

Gary

On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory  wrote:

> Git bisec says:
>
> *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit*
> commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a
> Author: Ralph Goers 
> Date:   Tue Jan 24 14:48:34 2017 -0700
>
> Use an ExecutorService to verify shutdown of the async threads
>
> :04 04 ad3cb23efafeaab2f7e934e249c8e53ff7dcf86f
> 056bbb158f43602fb2a4e8c74c5bcff29e5e5fe5 M  log4j-core
> bisect run success
>
>
> I'm not sure what needs to be reverted or changed but there you have it (I
> have to get back to a customer issue now).
>
> If you want to do this yourself you can run:
>
> git bisect start HEAD log4j-2.7
>
> (I was not sure how far back to go so I picked 2.7. It turns out I could
> have used 2.8. Then in a script called ..\run.cmd I have:
>
> call mvn clean
> call mvn -DskipTests -pl log4j-api install
> mvn -Dtest=RollingAppenderSizeTest -pl log4j-core test
>
> and run:
>
> git bisect run ..\run.cmd
>
> which gives you the output at the start of this message.
>
> Gary
>
>
> On Thu, Feb 2, 2017 at 5:01 PM, Gary Gregory 
> wrote:
>
>> I get:
>>
>> Tests in error:
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>   RollingAppenderSizeTest.cleanup:115->cleanFolder:189 ╗ FileSystem
>> target\rolli...
>>
>> Tests run: 1879, Failures: 0, Errors: 10, Skipped: 30
>>
>> using:
>>
>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> 2015-11-10T08:41:47-08:00)
>> Maven home: C:\Java\apache-maven-3.3.9\bin\..
>> Java version: 1.7.0_80, vendor: Oracle Corporation
>> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>>
>> Anyone else?
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 
>>
>> 
>> Spring Batch in Action
>> 
>> 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
>
> 
> JUnit in Action, Second Edition
> 
>
> 
> Spring Batch in Action
> 
> 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, 

[jira] [Commented] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[Matt Sicker (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863099#comment-15863099
 ] 

Matt Sicker commented on LOG4J2-1813:
-

That reminds me; I'd like to point out that LoggerContextRule in 
log4j-core:test interprets the system property "EBUG" as a debug switch 
({{-DEBUG}}). That class should be updated to support this proposed property as 
well for completeness sake.

> Provide shorter and more intuitive way to switch on Log4j internal debug 
> logging
> 
>
> Key: LOG4J2-1813
> URL: https://issues.apache.org/jira/browse/LOG4J2-1813
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.8
>Reporter: Remko Popma
>Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> People find it difficult to troubleshoot Log4j 2 configuration issues. Many 
> people don't know what the "status" attribute is for at the beginning of the 
> configuration:
> {code}
>  ...
> {code}
> In addition, the above setting does not take effect until the configuration 
> file is found. If users have trouble making Log4j 2 find their configuration 
> file, the above does not help.
> In such cases, users can enable internal status logging by setting system 
> property {{org.apache.logging.log4j.simplelog.StatusLogger.level}} to 
> {{TRACE}}.
> This is problematic because:
> * It is not well-known (documented in the FAQ and on the configuration page 
> but many people don't know about this feature)
> * The name is a bit... lengthy :-) 
> * Apparently people don't intuitively grasp that "status logging" means the 
> internal log4j 2 debug logging facility.
> * It is confusing that there are two phases (before config file found and 
> after), and the status logger level can be different and needs to be 
> specified separately
> I propose we add a short, intuitive system property that results in _all_ 
> internal Log4j 2 status logging to be printed to the console. When set, this 
> property should even override the configuration status attribute in my 
> opinion.
> Something like {{-Dlog4j2.debug}} (without even requiring a value) would be 
> good, but I'm open to any suggestions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[Remko Popma (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863065#comment-15863065
 ] 

Remko Popma commented on LOG4J2-1813:
-

That is certainly an improvement and I like the initiative. 

I would like to give the {{-Dlog4j2.debug}} switch special treatment: note that 
no value is required, just specifying the property is the equivalent of 
{{-Dlog4j2.simplelog.StatusLogger.level=TRACE}}, plus it should persist even if 
the configuration file has a different value in its {{status}} attribute. 

> Provide shorter and more intuitive way to switch on Log4j internal debug 
> logging
> 
>
> Key: LOG4J2-1813
> URL: https://issues.apache.org/jira/browse/LOG4J2-1813
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.8
>Reporter: Remko Popma
>Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> People find it difficult to troubleshoot Log4j 2 configuration issues. Many 
> people don't know what the "status" attribute is for at the beginning of the 
> configuration:
> {code}
>  ...
> {code}
> In addition, the above setting does not take effect until the configuration 
> file is found. If users have trouble making Log4j 2 find their configuration 
> file, the above does not help.
> In such cases, users can enable internal status logging by setting system 
> property {{org.apache.logging.log4j.simplelog.StatusLogger.level}} to 
> {{TRACE}}.
> This is problematic because:
> * It is not well-known (documented in the FAQ and on the configuration page 
> but many people don't know about this feature)
> * The name is a bit... lengthy :-) 
> * Apparently people don't intuitively grasp that "status logging" means the 
> internal log4j 2 debug logging facility.
> * It is confusing that there are two phases (before config file found and 
> after), and the status logger level can be different and needs to be 
> specified separately
> I propose we add a short, intuitive system property that results in _all_ 
> internal Log4j 2 status logging to be printed to the console. When set, this 
> property should even override the configuration status attribute in my 
> opinion.
> Something like {{-Dlog4j2.debug}} (without even requiring a value) would be 
> good, but I'm open to any suggestions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Remko travel plans

[Gary Gregory]

NL is great. Enjoy!

Gary

On Feb 12, 2017 6:31 AM, "Remko Popma"  wrote:

> I will be travelling to Holland between Feb 15 and March 5th, with
> sporadic internet access at times, so I may be slow to reply during this
> period.
>
> Remko
>

[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[Matt Sicker (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862963#comment-15862963
 ] 

Matt Sicker commented on LOG4J2-1812:
-

You'll want to use the normalised property name after LOG4J2-1431 is merged, 
though I don't really want to introduce a large change like that for 2.8.1.

> Improve error message when log4j 2 configuration file not found
> ---
>
> Key: LOG4J2-1812
> URL: https://issues.apache.org/jira/browse/LOG4J2-1812
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7, 2.8
>Reporter: Remko Popma
>Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> When configuration fails because no Log4j 2 configuration file is found, the 
> following message is logged to the console at ERROR level: 
> {code}
> No log4j2 configuration file found. Using default configuration: logging only 
> errors to the console.
> {code}
> We should be able to improve this. One idea is to add this:
> {code}
> No log4j2 configuration file found. Using default configuration: logging only 
> errors to the console. Set system property 
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show 
> Log4j2 internal initialization logging.
> {code}
> Another idea is to dump the contents of the StatusLogger ring buffer to the 
> console.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[Matt Sicker (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862962#comment-15862962
 ] 

Matt Sicker commented on LOG4J2-1813:
-

The simplified property system (which isn't merged yet btw) would support that 
long name as one of the following:

* {{log4j2.simplelog.StatusLogger.level}}
* {{log4j2.simplelogStatusLoggerLevel}}
* and many other combinations, yet the shortest possible property name for this 
would be:
* {{simplelogStatusLoggerLevel}}
* ...which is still pretty long.

> Provide shorter and more intuitive way to switch on Log4j internal debug 
> logging
> 
>
> Key: LOG4J2-1813
> URL: https://issues.apache.org/jira/browse/LOG4J2-1813
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.8
>Reporter: Remko Popma
>Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> People find it difficult to troubleshoot Log4j 2 configuration issues. Many 
> people don't know what the "status" attribute is for at the beginning of the 
> configuration:
> {code}
>  ...
> {code}
> In addition, the above setting does not take effect until the configuration 
> file is found. If users have trouble making Log4j 2 find their configuration 
> file, the above does not help.
> In such cases, users can enable internal status logging by setting system 
> property {{org.apache.logging.log4j.simplelog.StatusLogger.level}} to 
> {{TRACE}}.
> This is problematic because:
> * It is not well-known (documented in the FAQ and on the configuration page 
> but many people don't know about this feature)
> * The name is a bit... lengthy :-) 
> * Apparently people don't intuitively grasp that "status logging" means the 
> internal log4j 2 debug logging facility.
> * It is confusing that there are two phases (before config file found and 
> after), and the status logger level can be different and needs to be 
> specified separately
> I propose we add a short, intuitive system property that results in _all_ 
> internal Log4j 2 status logging to be printed to the console. When set, this 
> property should even override the configuration status attribute in my 
> opinion.
> Something like {{-Dlog4j2.debug}} (without even requiring a value) would be 
> good, but I'm open to any suggestions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[Matt Sicker (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862948#comment-15862948
 ] 

Matt Sicker commented on LOG4J2-1811:
-

I've been thinking about something similar lately, but I wasn't sure what the 
problem could be described as. I do have some ideas:

* Combine the Plugins and Extending Log4j manual pages. The split is hard to 
define, and the pages reference each other anyways.
* Possibly split up the appenders page so that each appender is a subpage. This 
idea might be applicable elsewhere, but having huge pages by default can be 
confusing. Perhaps generating both a per-page and single-page version of the 
manual would be a good idea? Not sure how easy that is to do with the current 
maven plugin.
* Replace code snippets, config snippets, etc., from manual with file includes 
of the actual source. This way, changes to tests/etc. will have documentation 
updates reflected.
* A tl;dr version of the manual would be neat. Give some sensible fast default 
config files to start with, maybe help point users in the right direction for 
advanced features.

> Log4j 2 configuration/usage ergonomics
> --
>
> Key: LOG4J2-1811
> URL: https://issues.apache.org/jira/browse/LOG4J2-1811
> Project: Log4j 2
>  Issue Type: Epic
>  Components: Configurators, Core
>Reporter: Remko Popma
>
> The vast majority of StackOverflow Log4j 2 questions is related to 
> configuration. The Log4j 2 site offers an extensive manual but apparently 
> many questions remain.
> This ticket aims to make Log4j 2 easier to configure and use. This can take 
> many forms: 
> * adding documentation
> * making documentation easier to find
> * detecting and addressing inconsistencies
> * facilitating debugging
> * showing richer error messages that help users diagnose problems
> * ... etc
> I am making this an epic so the effort can span multiple releases and include 
> many big or small changes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Logback performance improvements

[Matt Sicker]

I found a comment somewhere (probably an old comment) that asked why Log4j
2 even exists when you could just use JUL. I feel like maybe we should make
a JSR/JEP/whatever to deprecate JUL entirely.

On 12 February 2017 at 08:54, Remko Popma  wrote:

> #FriendsDontLetFriendsUseJavaUtilLogging
>
> On Sun, Feb 12, 2017 at 11:41 PM, Remko Popma 
> wrote:
>
>> But I agree it is interesting to see that a simple (RAF)FileAppender will
>> outperform async logging if the sustained logging rate is faster than the
>> appender can handle for long enough to fill up the queue. I've heard people
>> in the high performance computing world mention this but I hadn't seen
>> actual numbers until now.
>>
>> It is good to gain an intuition on these things. Async Loggers (with LMAX
>> Disruptor) performance is worse than a plain File but not terrible either.
>> Interesting how LogbackAsyncFile seems to suffer more than
>> log4j2AsyncAppender.
>>
>> And yes, JUL is so bad it is not funny any more. We did document that
>> 
>> but perhaps we need to evangelize it more...
>>
>>
>> On Sun, Feb 12, 2017 at 4:59 PM, Remko Popma 
>> wrote:
>>
>>> The queue is bigger but still fills up quickly because all the
>>> benchmarks do is add events as quickly as possible and the FileAppender
>>> can't keep up with that rate.
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 12, 2017, at 16:19, Apache  wrote:
>>>
>>> I added the tests so you guys could run them and take a look. I have no
>>> problem with the changes being reverted.
>>>
>>> As I think I said, I expected most of the async appenders to back up. I
>>> expected them to be a bit slower, but I didn’t expect them to be as slow as
>>> they are when the queue is full. I also don’t understand why AsyncLogger is
>>> slower as it should have a large ring buffer if I understand correctly.
>>>
>>> Ralph
>>>
>>> On Feb 11, 2017, at 4:36 PM, Remko Popma  wrote:
>>>
>>> I don't think it is a good idea to mix async tests with sync tests.
>>>
>>> We already have separate benchmarks for the various ways to log
>>> asynchronously, if you want to compare them just run those also.
>>>
>>> JMH makes it super easy to build benchmarks but we have to be very
>>> careful that the test really measures what we want to measure.
>>>
>>> Asynchronous logging has two "states", queue full and space available.
>>> Do we want to measure the queue full state or the space available state (or
>>> the transition between the two)?
>>>
>>> With a normal FileAppender JMH will iterate so fast that the queue
>>> immediately fills up. This will likely happen during the warmup iterations
>>> (no guarantee of course).
>>>
>>> What actually happens in that state? We used to block until space
>>> becomes available in the queue. What we do now depends on the configured
>>> AsyncQueueFullPolicy. Because blocking caused deadlocks in some scenarios,
>>> our current default is to bypass the queue and log to the FileAppender
>>> directly. I expect that to be slower than the simple FileAppender because
>>> of the additional lock contention on the tail of the queue during the
>>> attempted thread handover.
>>>
>>> The "queue full" state is not the normal logging state for an
>>> application. If we want to measure this we should move these tests to a
>>> separate benchmark that is clearly marked "QueueFullAsyncBenchmark" or
>>> something like that.
>>> Otherwise people reading these benchmark results will misinterpret them
>>> and get confused.
>>>
>>> The existing Async benchmarks ensure they measure the "queue space
>>> available" state.
>>>
>>> Remko
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 12, 2017, at 4:37, Apache  wrote:
>>>
>>> Just for fun I decided to add some more tests to the file appender
>>> benchmark. I’ve checked them in. Please review them to see if everything is
>>> configured so the tests make sense.
>>>
>>> Note that I would expect the async appenders to reduce to the speed of
>>> the file appender, since once the queue fills up that is what they are
>>> waiting on. But I didn’t set a buffer size for the disruptor or async
>>> logger tests so I would have expected those to be quite a bit faster than
>>> the regular file test.
>>>
>>> The one thing that is definitely worth noting is how truly terrible the
>>> JUL file appender is. I have to assume that it must be doing an immediate
>>> flush on every write.
>>>
>>> This is on my MacBook Pro - what Ceki would call Fast CPU/Fast SSD
>>>
>>> Benchmark  Mode  Samples
>>> Score Error   Units
>>> o.a.l.l.p.j.FileAppenderBenchmark.julFile thrpt
>>> 1069.546 ±   2.635  ops/ms
>>> o.a.l.l.p.j.FileAppenderBenchmark.log4j1File  thrpt
>>> 10   783.006 ±  28.138  ops/ms
>>> 

Re: Remko travel plans

[Matt Sicker]

Have a good time!

On 12 February 2017 at 09:29, Apache  wrote:

> Safe travels. I hop you enjoy your time there.
>
> Ralph
>
> > On Feb 12, 2017, at 7:30 AM, Remko Popma  wrote:
> >
> > I will be travelling to Holland between Feb 15 and March 5th, with
> sporadic internet access at times, so I may be slow to reply during this
> period.
> >
> > Remko
>
>
>
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>
>


-- 
Matt Sicker 

Re: Remko travel plans

[Apache]

Safe travels. I hop you enjoy your time there.

Ralph

> On Feb 12, 2017, at 7:30 AM, Remko Popma  wrote:
> 
> I will be travelling to Holland between Feb 15 and March 5th, with sporadic 
> internet access at times, so I may be slow to reply during this period.
> 
> Remko



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Logback performance improvements

[Remko Popma]

#FriendsDontLetFriendsUseJavaUtilLogging

On Sun, Feb 12, 2017 at 11:41 PM, Remko Popma  wrote:

> But I agree it is interesting to see that a simple (RAF)FileAppender will
> outperform async logging if the sustained logging rate is faster than the
> appender can handle for long enough to fill up the queue. I've heard people
> in the high performance computing world mention this but I hadn't seen
> actual numbers until now.
>
> It is good to gain an intuition on these things. Async Loggers (with LMAX
> Disruptor) performance is worse than a plain File but not terrible either.
> Interesting how LogbackAsyncFile seems to suffer more than
> log4j2AsyncAppender.
>
> And yes, JUL is so bad it is not funny any more. We did document that
> 
> but perhaps we need to evangelize it more...
>
>
> On Sun, Feb 12, 2017 at 4:59 PM, Remko Popma 
> wrote:
>
>> The queue is bigger but still fills up quickly because all the benchmarks
>> do is add events as quickly as possible and the FileAppender can't keep up
>> with that rate.
>>
>> Sent from my iPhone
>>
>> On Feb 12, 2017, at 16:19, Apache  wrote:
>>
>> I added the tests so you guys could run them and take a look. I have no
>> problem with the changes being reverted.
>>
>> As I think I said, I expected most of the async appenders to back up. I
>> expected them to be a bit slower, but I didn’t expect them to be as slow as
>> they are when the queue is full. I also don’t understand why AsyncLogger is
>> slower as it should have a large ring buffer if I understand correctly.
>>
>> Ralph
>>
>> On Feb 11, 2017, at 4:36 PM, Remko Popma  wrote:
>>
>> I don't think it is a good idea to mix async tests with sync tests.
>>
>> We already have separate benchmarks for the various ways to log
>> asynchronously, if you want to compare them just run those also.
>>
>> JMH makes it super easy to build benchmarks but we have to be very
>> careful that the test really measures what we want to measure.
>>
>> Asynchronous logging has two "states", queue full and space available. Do
>> we want to measure the queue full state or the space available state (or
>> the transition between the two)?
>>
>> With a normal FileAppender JMH will iterate so fast that the queue
>> immediately fills up. This will likely happen during the warmup iterations
>> (no guarantee of course).
>>
>> What actually happens in that state? We used to block until space becomes
>> available in the queue. What we do now depends on the configured
>> AsyncQueueFullPolicy. Because blocking caused deadlocks in some scenarios,
>> our current default is to bypass the queue and log to the FileAppender
>> directly. I expect that to be slower than the simple FileAppender because
>> of the additional lock contention on the tail of the queue during the
>> attempted thread handover.
>>
>> The "queue full" state is not the normal logging state for an
>> application. If we want to measure this we should move these tests to a
>> separate benchmark that is clearly marked "QueueFullAsyncBenchmark" or
>> something like that.
>> Otherwise people reading these benchmark results will misinterpret them
>> and get confused.
>>
>> The existing Async benchmarks ensure they measure the "queue space
>> available" state.
>>
>> Remko
>>
>> Sent from my iPhone
>>
>> On Feb 12, 2017, at 4:37, Apache  wrote:
>>
>> Just for fun I decided to add some more tests to the file appender
>> benchmark. I’ve checked them in. Please review them to see if everything is
>> configured so the tests make sense.
>>
>> Note that I would expect the async appenders to reduce to the speed of
>> the file appender, since once the queue fills up that is what they are
>> waiting on. But I didn’t set a buffer size for the disruptor or async
>> logger tests so I would have expected those to be quite a bit faster than
>> the regular file test.
>>
>> The one thing that is definitely worth noting is how truly terrible the
>> JUL file appender is. I have to assume that it must be doing an immediate
>> flush on every write.
>>
>> This is on my MacBook Pro - what Ceki would call Fast CPU/Fast SSD
>>
>> Benchmark  Mode  Samples
>> Score Error   Units
>> o.a.l.l.p.j.FileAppenderBenchmark.julFile thrpt
>> 1069.546 ±   2.635  ops/ms
>> o.a.l.l.p.j.FileAppenderBenchmark.log4j1File  thrpt   10
>>   783.006 ±  28.138  ops/ms
>> o.a.l.l.p.j.FileAppenderBenchmark.log4j2AsyncAppender thrpt   10
>>   939.605 ±  38.655  ops/ms
>> o.a.l.l.p.j.FileAppenderBenchmark.log4j2AsyncDisruptorthrpt
>> 10  1446.522 ±  45.485  ops/ms
>> o.a.l.l.p.j.FileAppenderBenchmark.log4j2AsyncLogger   thrpt
>> 10  1269.014 ±  27.236  ops/ms
>> o.a.l.l.p.j.FileAppenderBenchmark.log4j2File  thrpt
>> 10  

Re: Logback performance improvements

[Remko Popma]

But I agree it is interesting to see that a simple (RAF)FileAppender will
outperform async logging if the sustained logging rate is faster than the
appender can handle for long enough to fill up the queue. I've heard people
in the high performance computing world mention this but I hadn't seen
actual numbers until now.

It is good to gain an intuition on these things. Async Loggers (with LMAX
Disruptor) performance is worse than a plain File but not terrible either.
Interesting how LogbackAsyncFile seems to suffer more than
log4j2AsyncAppender.

And yes, JUL is so bad it is not funny any more. We did document that

but perhaps we need to evangelize it more...


On Sun, Feb 12, 2017 at 4:59 PM, Remko Popma  wrote:

> The queue is bigger but still fills up quickly because all the benchmarks
> do is add events as quickly as possible and the FileAppender can't keep up
> with that rate.
>
> Sent from my iPhone
>
> On Feb 12, 2017, at 16:19, Apache  wrote:
>
> I added the tests so you guys could run them and take a look. I have no
> problem with the changes being reverted.
>
> As I think I said, I expected most of the async appenders to back up. I
> expected them to be a bit slower, but I didn’t expect them to be as slow as
> they are when the queue is full. I also don’t understand why AsyncLogger is
> slower as it should have a large ring buffer if I understand correctly.
>
> Ralph
>
> On Feb 11, 2017, at 4:36 PM, Remko Popma  wrote:
>
> I don't think it is a good idea to mix async tests with sync tests.
>
> We already have separate benchmarks for the various ways to log
> asynchronously, if you want to compare them just run those also.
>
> JMH makes it super easy to build benchmarks but we have to be very careful
> that the test really measures what we want to measure.
>
> Asynchronous logging has two "states", queue full and space available. Do
> we want to measure the queue full state or the space available state (or
> the transition between the two)?
>
> With a normal FileAppender JMH will iterate so fast that the queue
> immediately fills up. This will likely happen during the warmup iterations
> (no guarantee of course).
>
> What actually happens in that state? We used to block until space becomes
> available in the queue. What we do now depends on the configured
> AsyncQueueFullPolicy. Because blocking caused deadlocks in some scenarios,
> our current default is to bypass the queue and log to the FileAppender
> directly. I expect that to be slower than the simple FileAppender because
> of the additional lock contention on the tail of the queue during the
> attempted thread handover.
>
> The "queue full" state is not the normal logging state for an application.
> If we want to measure this we should move these tests to a separate
> benchmark that is clearly marked "QueueFullAsyncBenchmark" or something
> like that.
> Otherwise people reading these benchmark results will misinterpret them
> and get confused.
>
> The existing Async benchmarks ensure they measure the "queue space
> available" state.
>
> Remko
>
> Sent from my iPhone
>
> On Feb 12, 2017, at 4:37, Apache  wrote:
>
> Just for fun I decided to add some more tests to the file appender
> benchmark. I’ve checked them in. Please review them to see if everything is
> configured so the tests make sense.
>
> Note that I would expect the async appenders to reduce to the speed of the
> file appender, since once the queue fills up that is what they are waiting
> on. But I didn’t set a buffer size for the disruptor or async logger tests
> so I would have expected those to be quite a bit faster than the regular
> file test.
>
> The one thing that is definitely worth noting is how truly terrible the
> JUL file appender is. I have to assume that it must be doing an immediate
> flush on every write.
>
> This is on my MacBook Pro - what Ceki would call Fast CPU/Fast SSD
>
> Benchmark  Mode  Samples
>   Score Error   Units
> o.a.l.l.p.j.FileAppenderBenchmark.julFile thrpt   10
>   69.546 ±   2.635  ops/ms
> o.a.l.l.p.j.FileAppenderBenchmark.log4j1File  thrpt   10
>   783.006 ±  28.138  ops/ms
> o.a.l.l.p.j.FileAppenderBenchmark.log4j2AsyncAppender thrpt   10
>   939.605 ±  38.655  ops/ms
> o.a.l.l.p.j.FileAppenderBenchmark.log4j2AsyncDisruptorthrpt   10
> 1446.522 ±  45.485  ops/ms
> o.a.l.l.p.j.FileAppenderBenchmark.log4j2AsyncLogger   thrpt   10
> 1269.014 ±  27.236  ops/ms
> o.a.l.l.p.j.FileAppenderBenchmark.log4j2File  thrpt   10
> 1475.605 ±  74.675  ops/ms
> o.a.l.l.p.j.FileAppenderBenchmark.log4j2MMF   thrpt   10
> 2131.240 ± 114.184  ops/ms
> o.a.l.l.p.j.FileAppenderBenchmark.log4j2RAF   thrpt   10
> 1499.667 ±  39.668  

Remko travel plans

[Remko Popma]

I will be travelling to Holland between Feb 15 and March 5th, with sporadic
internet access at times, so I may be slow to reply during this period.

Remko