Re: Remko travel plans

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

Re: Logback performance improvements

#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

Re: Remko travel plans

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

Remko travel plans

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

Re: Logback performance improvements

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

Re: Logback performance improvements

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: >

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

[ 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)

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

[ 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.

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

[ 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

Re: Remko travel plans

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

[ 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

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

[ 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

Re: RollingAppenderSizeTest failures

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. > >

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

See -- Started by upstream project "Log4j" build number 2 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment variables. Building

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

See -- Started by upstream project "Log4j" build number 2 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment variables. Building

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

See Changes: [Matt Sicker] Add maven wrapper script -- Started by upstream project "Log4j" build number 4 originally caused by: Started by user Matt Sicker

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

See Changes: [Matt Sicker] Add maven wrapper script -- Started by upstream project "Log4j" build number 4 originally caused by: Started by user Matt Sicker

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

See Changes: [Matt Sicker] Add maven wrapper script -- Started by upstream project "Log4j" build number 4 originally caused by: Started by

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

See Changes: [Matt Sicker] Add maven wrapper script -- Started by upstream project "Log4j" build number 4 originally caused by: Started by

Jenkins build is back to normal : Log4jScala #19

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.8 (unlimited security) 64-bit Windows only #1

See -- Started by upstream project "Log4j" build number 1 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment

Re: RollingAppenderSizeTest failures

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

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

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

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

See -- Started by upstream project "Log4j" build number 1 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment

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

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:

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

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:

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

See Changes: [Matt Sicker] Try out specifying bash in mvnw to make Jenkins happy -- Started by upstream project "Log4j" build number 5

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

See Changes: [Matt Sicker] Try out specifying bash in mvnw to make Jenkins happy -- Started by upstream project "Log4j" build number 5

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

See -- Started by upstream project "Log4j" build number 6 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment

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

See -- Started by upstream project "Log4j" build number 6 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment variables. Building

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

See -- Started by upstream project "Log4j" build number 6 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment

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

See -- Started by upstream project "Log4j" build number 6 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment variables. Building

Re: RollingAppenderSizeTest failures

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

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

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

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

See -- Started by upstream project "Log4j" build number 3 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment

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

See -- Started by upstream project "Log4j" build number 3 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment

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

See -- Started by upstream project "Log4j" build number 3 originally caused by: Started by user Matt Sicker [EnvInject] - Loading node environment variables. Building

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

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:

Re: RollingAppenderSizeTest failures

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

Re: RollingAppenderSizeTest failures

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

Re: RollingAppenderSizeTest failures

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

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

See -- [...truncated 15999 lines...] 2017-02-13 07:20:05,280 main DEBUG Starting FileManager

Re: RollingAppenderSizeTest failures

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:

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

See -- [...truncated 16055 lines...] 2017-02-13 07:21:58,777 main DEBUG Starting OutputStreamManager