[jira] [Updated] (LOG4J2-1040) Update MongoDB driver from 2.13.2 to 3.0.2

[ https://issues.apache.org/jira/browse/LOG4J2-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1040: Fix Version/s: (was: 2.4) 2.4.1 > Update MongoDB driver from 2.13.2 to 3.0.2

[jira] [Updated] (LOG4J2-1095) How can we have multiple Configurations?

[ https://issues.apache.org/jira/browse/LOG4J2-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1095: Fix Version/s: (was: 2.4) 2.4.1 > How can we have multiple Configurations? >

[jira] [Updated] (LOG4J2-1124) LogManager.getLogger()

[ https://issues.apache.org/jira/browse/LOG4J2-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1124: Fix Version/s: (was: 2.4) 2.4.1 > LogManager.getLogger() > -

Jenkins build is back to stable : Log4j 2.x #1403

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[VOTE][Result] Log4j 2.4 rc1

72 hours has passed and the vote received 3 binding +1 votes from Remko Popma, Gary Gregory, and Ralph Goers. A non-binding +1 was received from Mikael Ståldal. There were no other votes. I will continue on and complete the release process. Ralph

[jira] [Closed] (LOG4J2-1131) Update mongo-java-driver from 2.13.2 to 2.13.3

[ https://issues.apache.org/jira/browse/LOG4J2-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1131. Resolution: Fixed org.apache.logging.log4j.nosql.appender.MongoDbTest passes with MongoDB 3.0.6 on

[jira] [Updated] (LOG4J2-1131) Update mongo-java-driver from 2.13.2 to 2.13.3

[ https://issues.apache.org/jira/browse/LOG4J2-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1131: - Fix Version/s: 2.4.1 Component/s: Appenders > Update mongo-java-driver from 2.13.2 to 2.13.

[jira] [Created] (LOG4J2-1131) Update mongo-java-driver from 2.13.2 to 2.13.3

Gary Gregory created LOG4J2-1131: Summary: Update mongo-java-driver from 2.13.2 to 2.13.3 Key: LOG4J2-1131 URL: https://issues.apache.org/jira/browse/LOG4J2-1131 Project: Log4j 2 Issue Type:

Jenkins build became unstable: Log4j 2.x #1402

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: logging-log4j2 git commit: Add article.

Yeah, maybe, but I'd probably rewrite the whole thing with full examples. At that point, I'd just put it on my blog and be done with it. At this point, I plan on dripping posts on what's new in 2.4. Gary On Wed, Sep 23, 2015 at 4:52 PM, Ralph Goers wrote: > Gary, > > Maybe you could offer to ed

Re: [VOTE] Log4j 2.4 rc1

I know that but for the sake of transparency I want to ack that we do get random errora from time to time, and here is one, with Murphy's Law saying "boo" in the middle of a RC VOTE thread. My guess is that the machine is busy and that this is some timing issue in the test itself, not the productio

Jenkins build is back to stable : Log4j 2.x #1401

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: logging-log4j2 git commit: Add article.

Gary, Maybe you could offer to edit this guy’s article. It is painful to read. Ralph > On Sep 23, 2015, at 3:21 PM, [email protected] wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 936fffb47 -> 563d55e85 > > > Add article. > > Project: http://git-wip-us.apac

Re: [VOTE] Log4j 2.4 rc1

This shouldn’t be on the vote thread. Nothing has changed in the FlumeAppender in a very long time. Ralph > On Sep 23, 2015, at 4:09 PM, Gary Gregory wrote: > > Note: > https://builds.apache.org/job/Log4j%202.x/1400/org.apache.logging.log4j$log4j-flume-ng/testReport/org.apache.logging.log4j.f

Re: [VOTE] Log4j 2.4 rc1

Note: https://builds.apache.org/job/Log4j%202.x/1400/org.apache.logging.log4j$log4j-flume-ng/testReport/org.apache.logging.log4j.flume.appender/FlumePersistentAppenderTest/testMultipleConcurrent/ I imagine this is just a timing issue? Gary On Sun, Sep 20, 2015 at 7:04 PM, Ralph Goers wrote: >

Jenkins build became unstable: Log4j 2.x #1400

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Commented] (LOG4J2-1130) CsvLogEventLayout NanoTime timestamp is always zero.

[ https://issues.apache.org/jira/browse/LOG4J2-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905282#comment-14905282 ] Gary Gregory commented on LOG4J2-1130: -- Remko: thank you tracking this issue. It fe

Re: [VOTE] Log4j 2.4 rc1

+1 Builds OK from distribution src zip. Distribution src zip MD5, SHA1 OK. ASC verifies OK. My test beds: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) Maven home: C:\Java\apache-maven-3.3.3\bin\.. Java version: 1.7.0_79, vendor: Oracle Corporation Java

[jira] [Commented] (LOG4J2-1126) Site fixes/improvements for 2.4 release

[ https://issues.apache.org/jira/browse/LOG4J2-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905263#comment-14905263 ] Gary Gregory commented on LOG4J2-1126: -- Thank you Remko for a great TODO list! > Si

Re: [VOTE] Log4j 2.4 rc1

Here is my +1. This vote would normally close 5 hours from now. However we only have 2 binding +1 votes as of now (in addition to a non-binding +1). Ralph > On Sep 20, 2015, at 7:04 PM, Ralph Goers wrote: > > This is a vote to release Log4j 2.4, the next version of the Log4j 2 project. > > P

[jira] [Closed] (LOG4J2-1126) Site fixes/improvements for 2.4 release

[ https://issues.apache.org/jira/browse/LOG4J2-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1126. --- > Site fixes/improvements for 2.4 release > --- > > K

[jira] [Resolved] (LOG4J2-1126) Site fixes/improvements for 2.4 release

[ https://issues.apache.org/jira/browse/LOG4J2-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1126. - Resolution: Fixed Fix Version/s: 2.4.1 Created separate issue LOG4J2-1130 for the CsvLogEv

[jira] [Created] (LOG4J2-1130) CsvLogEventLayout NanoTime timestamp is always zero.

Remko Popma created LOG4J2-1130: --- Summary: CsvLogEventLayout NanoTime timestamp is always zero. Key: LOG4J2-1130 URL: https://issues.apache.org/jira/browse/LOG4J2-1130 Project: Log4j 2 Issue Ty

[jira] [Resolved] (LOG4J2-1129) Allow one of a number of patterns to be used in PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1129. - Resolution: Fixed Fix committed. > Allow one of a number of patterns to be used in PatternLayout

[jira] [Created] (LOG4J2-1129) Allow one of a number of patterns to be used in PatternLayout

Ralph Goers created LOG4J2-1129: --- Summary: Allow one of a number of patterns to be used in PatternLayout Key: LOG4J2-1129 URL: https://issues.apache.org/jira/browse/LOG4J2-1129 Project: Log4j 2