Re: [VOTE] Log4j 2.6.2 rc1

What about https://issues.apache.org/jira/browse/LOG4J2-1452 On Wed, Jul 6, 2016 at 7:53 AM, Ralph Goers wrote: > This is a vote to release Log4j 2.6.2, the next version of the Log4j 2 > project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the ar

Re: [VOTE] Log4j 2.6.2 rc1

Seems like the top four entries in changes.xml is not included in the release notes: If copy and delete fails in rename action then resort to truncating the source file after copying it. CronTriggeringPolicy was not properly setting the prevFileTime value for the PatternProcessor so file

Re: [VOTE] Log4j 2.6.2 rc1

Good catch! Ah, the joys of copy-paste... Looks like these entries all are missing the type attribute (add, fix, update) We can manually update the announcement before mailing it out. Sent from my iPhone > On 2016/07/06, at 16:56, Mikael Ståldal wrote: > > Seems like the top four entrie

Re: log4j2 evangelism

> I updated the Apache Logging page to mention that Log4j 1 is EOL. > I added the EOL announcement to the top of all main pages in the Log4j 1 site. Should we do the same for "Apache log4j 1 extras"? On Sat, Jul 2, 2016 at 3:57 PM, Remko Popma wrote: > > > On Mon, Jun 13, 2016 at 11:52 PM, Remk

Re: [VOTE] Log4j 2.6.2 rc1

+1 given that we update the release notes to include the missing issues. On Wed, Jul 6, 2016 at 10:26 AM, Remko Popma wrote: > Good catch! Ah, the joys of copy-paste... > > Looks like these entries all are missing the type attribute (add, fix, > update) > > We can manually update the announc

Re: [VOTE] Log4j 2.6.2 rc1

To be clear, we can’t update the release notes that are part of the released bundles and in the tag since that would require a new build. We can update the release announcement and I can manually update the web site to include them. Ralph > On Jul 6, 2016, at 4:45 AM, Mikael Ståldal wrote: >

Re: [VOTE] Log4j 2.6.2 rc1

OK, +1 On Wed, Jul 6, 2016 at 2:32 PM, Ralph Goers wrote: > To be clear, we can’t update the release notes that are part of the > released bundles and in the tag since that would require a new build. We > can update the release announcement and I can manually update the web site > to include the

Re: [VOTE] Log4j 2.6.2 rc1

Should we fix the changes.xml file now? On Wed, Jul 6, 2016 at 10:26 AM, Remko Popma wrote: > Good catch! Ah, the joys of copy-paste... > > Looks like these entries all are missing the type attribute (add, fix, > update) > > We can manually update the announcement before mailing it out. > >

[jira] [Created] (LOG4J2-1457) Class loader deadlock when using async logging

Leon Finker created LOG4J2-1457: --- Summary: Class loader deadlock when using async logging Key: LOG4J2-1457 URL: https://issues.apache.org/jira/browse/LOG4J2-1457 Project: Log4j 2 Issue Type: Bu

[jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker updated LOG4J2-1457: Attachment: threaddump.txt > Class loader deadlock when using async logging > -

Re: [VOTE] Log4j 2.6.2 rc1

Is the JIRA report page ever going to be useful? https://rgoers.github.io/log4j2-site/jira-report.html Or could we just remove it in favor of the manual changelog? * Site and docs look good. * GPG keys file imports properly (I've seen some projects fail on that and still haven't noticed). * Diggi

Re: [jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

Although I'm still not clear why it deadlocks. I can confirm the thread in is logging an exception. But if the AsyncLogger thread picked up this same event (assumption), why the thread in doesn't continue... On 2016-07-06 10:57 (-0400), "Leon Finker (JIRA)" wrote: > > [ > https://issu

Re: [VOTE] Log4j 2.6.2 rc1

Yes, it should be fixed. Ralph > On Jul 6, 2016, at 6:02 AM, Mikael Ståldal wrote: > > Should we fix the changes.xml file now? > > On Wed, Jul 6, 2016 at 10:26 AM, Remko Popma > wrote: > Good catch! Ah, the joys of copy-paste... > > Looks like these entries all

Re: [VOTE] Log4j 2.6.2 rc1

Tested, no issues observed. +1 On 2016-07-06 11:23 (-0400), Ralph Goers wrote: > Yes, it should be fixed. > > Ralph > > > On Jul 6, 2016, at 6:02 AM, Mikael Ståldal > > wrote: > > > > Should we fix the changes.xml file now? > > > > On Wed, Jul 6, 2016 at 10:26 AM, Remko Popma >

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364522#comment-15364522 ] Ralph Goers commented on LOG4J2-1457: - The workaround for this would be to modify you

Re: [jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

Do you know what the exception is and where it originated from? Does it correlate in any way to the other threads that are marked as runnable? Ralph > On Jul 6, 2016, at 8:14 AM, Leon Finker wrote: > > Although I'm still not clear why it deadlocks. I can confirm the thread in > is logging a

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364613#comment-15364613 ] Leon Finker commented on LOG4J2-1457: - Yes it looks like many of those threads are lo

Re: [jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

This application doesn't create any other class loaders besides the standard. It's regular JVM app (not tomcat or any other hosted process). According to: http://docs.oracle.com/javase/7/docs/technotes/guides/lang/cl-mt.html The class loading lock is done on class loader + class name since Java

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364804#comment-15364804 ] Ralph Goers commented on LOG4J2-1457: - I found https://bugs.openjdk.java.net/browse/J

[jira] [Comment Edited] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364804#comment-15364804 ] Ralph Goers edited comment on LOG4J2-1457 at 7/6/16 6:23 PM: -

Re: [VOTE] Log4j 2.6.2 rc1

There is one Clirr failure in the API: [ERROR] 7009: org.apache.logging.log4j.util.Unbox: Accessibility of method 'public Unbox()' has been decreased from public to private This is not documented in the release note and I am guessing not in JIRA either. Gary On Tue, Jul 5, 2016 at 10:53 PM, Ral

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364943#comment-15364943 ] Leon Finker commented on LOG4J2-1457: - Any reason that we need to run the class initi

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364978#comment-15364978 ] Ralph Goers commented on LOG4J2-1457: - That is a very good observation. Do you think

Re: [VOTE] Log4j 2.6.2 rc1

Even with that I am +1 (because the Clirr break is in a util package and it would be unusual to instantiate this class) >From src zip distro, MD5, SHA1, ASC OK. RAT and Clirr checks OK. Building jars OK, running tests OK. Building site is OK. Gary On Wed, Jul 6, 2016 at 11:29 AM, Gary Gregory

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365057#comment-15365057 ] Leon Finker commented on LOG4J2-1457: - I was able to reproduce it consistently in deb

[jira] [Comment Edited] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365057#comment-15365057 ] Leon Finker edited comment on LOG4J2-1457 at 7/6/16 8:58 PM: -

[jira] [Created] (LOG4J2-1458) Update Jackson from 2.7.5 to 2.8.0

Gary Gregory created LOG4J2-1458: Summary: Update Jackson from 2.7.5 to 2.8.0 Key: LOG4J2-1458 URL: https://issues.apache.org/jira/browse/LOG4J2-1458 Project: Log4j 2 Issue Type: New Feature

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

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

[jira] [Closed] (LOG4J2-1458) Update Jackson from 2.7.5 to 2.8.0

[ https://issues.apache.org/jira/browse/LOG4J2-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1458. Resolution: Fixed In Git master. > Update Jackson from 2.7.5 to 2.8.0 > --

[jira] [Updated] (LOG4J2-1459) [PatternLayout] Add an ANSI option to %message

[ https://issues.apache.org/jira/browse/LOG4J2-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1459: - Description: For {{PatternLayout}}: Add an ANSI option to {{message}} so you can say {{%message\

[jira] [Created] (LOG4J2-1459) [PatternLayout] Add an ANSI option to %message

Gary Gregory created LOG4J2-1459: Summary: [PatternLayout] Add an ANSI option to %message Key: LOG4J2-1459 URL: https://issues.apache.org/jira/browse/LOG4J2-1459 Project: Log4j 2 Issue Type:

[jira] [Updated] (LOG4J2-1459) [PatternLayout] Add an ANSI option to %message

[ https://issues.apache.org/jira/browse/LOG4J2-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1459: - Description: For {{PatternLayout}}: Add an ANSI option to {{message}} so you can say {{%message\

Re: [VOTE] Log4j 2.6.2 rc1

The web site is corrected. It had the 4 items but with an odd icon. I’ve updated changes.xml and RELEASE_NOTES.txt. While they won’t be in the release distribution RELEASE_NOTES.txt is used for the announcement email. Ralph > On Jul 6, 2016, at 8:23 AM, Ralph Goers wrote: > > Yes, it should

Build failed in Jenkins: Log4j 2.x #2092

See Changes: [rgoers] Fix changes.xml and update release notes -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu3 (Ubuntu ubuntu legacy-ubuntu)