Re: Towards a 2.1 release

Gary mentioned that in Commons they have multiple versions on the site so he suggested using that profile/maven plugin. That said, this may not be easy and will probably be significant work. As Gary said, we're all in agreement we can do a 2.1 release, so there's no need to look into the impli

Re: Towards a 2.1 release

Matt, It seems like the consensus is to skip a beta. You may want to send a [poll] email and get a more formal feel for it. Gary On Mon, Sep 22, 2014 at 2:16 PM, Matt Sicker wrote: > How would I even be able to release the beta artifacts? The "release" > profile doesn't seem appropriate. > >

[jira] [Commented] (LOG4J2-506) Binary logging interface

[ https://issues.apache.org/jira/browse/LOG4J2-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143867#comment-14143867 ] Matt Sicker commented on LOG4J2-506: That Encoder interface is a lot like WritableByte

Re: Towards a 2.1 release

I guess you'll need Ralph's help on how he did it before. Gary On Mon, Sep 22, 2014 at 2:16 PM, Matt Sicker wrote: > How would I even be able to release the beta artifacts? The "release" > profile doesn't seem appropriate. > > On 22 September 2014 12:15, Remko Popma wrote: > >> I'm also fine w

Re: Towards a 2.1 release

How would I even be able to release the beta artifacts? The "release" profile doesn't seem appropriate. On 22 September 2014 12:15, Remko Popma wrote: > I'm also fine with just doing a 2.1 and following up with 2.1.x releases > if issues are found. > > On Tue, Sep 23, 2014 at 2:01 AM, Matt Sicke

[jira] [Created] (LOG4J2-854) Use java 8 doclet to generate log4j Javadoc

Remko Popma created LOG4J2-854: -- Summary: Use java 8 doclet to generate log4j Javadoc Key: LOG4J2-854 URL: https://issues.apache.org/jira/browse/LOG4J2-854 Project: Log4j 2 Issue Type: Improvem

Re: Towards a 2.1 release

I'm also fine with just doing a 2.1 and following up with 2.1.x releases if issues are found. On Tue, Sep 23, 2014 at 2:01 AM, Matt Sicker wrote: > Unless we have some way to have more than one release on the site, making > it 2.1 might be our best bet. > > On 22 September 2014 11:01, Remko Popm

[jira] [Created] (LOG4J2-853) [Perf] Task: identify hotspots/bottlenecks in a profiler

Remko Popma created LOG4J2-853: -- Summary: [Perf] Task: identify hotspots/bottlenecks in a profiler Key: LOG4J2-853 URL: https://issues.apache.org/jira/browse/LOG4J2-853 Project: Log4j 2 Issue Ty

[jira] [Created] (LOG4J2-852) [Perf] Use FastDateFormat to format %d timestamps

Remko Popma created LOG4J2-852: -- Summary: [Perf] Use FastDateFormat to format %d timestamps Key: LOG4J2-852 URL: https://issues.apache.org/jira/browse/LOG4J2-852 Project: Log4j 2 Issue Type: Imp

Re: Towards a 2.1 release

I think it is a matter of confidence. The API module is solid. If something outside of the API needs fixing, we can do so quickly without worrying about being handcuffed by BC. Since I am not the RM I would suggest a beta this week and 2.1 within 1 week after. Folks that are paying attention wil

Re: Towards a 2.1 release

Unless we have some way to have more than one release on the site, making it 2.1 might be our best bet. On 22 September 2014 11:01, Remko Popma wrote: > Do we need to have a 2.1-beta release, or shall we just do a 2.1 release > (and follow up with 2.1.1 etc if issues are found)? > > When are we

[jira] [Updated] (LOG4J2-850) [Perf] Add performance tests for MemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-850: --- Component/s: (was: Core) Appenders > [Perf] Add performance tests for MemoryMappe

[jira] [Updated] (LOG4J2-849) [Perf] Add performance tests to compare overhead of various logging APIs

[ https://issues.apache.org/jira/browse/LOG4J2-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-849: --- Component/s: SLF4J Bridge > [Perf] Add performance tests to compare overhead of various logging APIs >

[jira] [Updated] (LOG4J2-849) [Perf] Add performance tests to compare overhead of various logging APIs

[ https://issues.apache.org/jira/browse/LOG4J2-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-849: --- Component/s: log4j 1.2 emulation JUL adapter JCL Bridge

[jira] [Created] (LOG4J2-851) Create RollingMemoryMappedFileAppender

Remko Popma created LOG4J2-851: -- Summary: Create RollingMemoryMappedFileAppender Key: LOG4J2-851 URL: https://issues.apache.org/jira/browse/LOG4J2-851 Project: Log4j 2 Issue Type: Improvement

[jira] [Created] (LOG4J2-850) [Perf] Add performance tests for MemoryMappedFileAppender

Remko Popma created LOG4J2-850: -- Summary: [Perf] Add performance tests for MemoryMappedFileAppender Key: LOG4J2-850 URL: https://issues.apache.org/jira/browse/LOG4J2-850 Project: Log4j 2 Issue T

[jira] [Created] (LOG4J2-849) [Perf] Add performance tests to compare overhead of various logging APIs

Remko Popma created LOG4J2-849: -- Summary: [Perf] Add performance tests to compare overhead of various logging APIs Key: LOG4J2-849 URL: https://issues.apache.org/jira/browse/LOG4J2-849 Project: Log4j 2

Towards a 2.1 release

Do we need to have a 2.1-beta release, or shall we just do a 2.1 release (and follow up with 2.1.1 etc if issues are found)? When are we aiming to do this release? There are still ~10 open Jira tickets targetting 2.1. Please take a look to see if that list is up to date.

[jira] [Resolved] (LOG4J2-807) Disruptor is null when configuration is reloaded (asyncRoot + monitorInterval)

[ https://issues.apache.org/jira/browse/LOG4J2-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-807. Resolution: Fixed Fixed in master in commits 0f8acc5 and 23b48b3. Please verify and close. > Disrup

Re: [2/2] git commit: Javadoc: Replace @doubt with TODO tags. Custom @'s in Javadoc 8 are not allowed unpackaged and then must exist, and we do not have them, so just use a "TODO" tag which can then b

I mean that I cannot get values for "%n" and "%d{UNIX}" in a header or footer. I was trying to use %n and it did not work so I tried %d{UNIX} just to see what would happen and it did not work either. Looking at the code, this is not surprising since the enhancement implemented in LOG4J-496 only c

Re: [2/2] git commit: Javadoc: Replace @doubt with TODO tags. Custom @'s in Javadoc 8 are not allowed unpackaged and then must exist, and we do not have them, so just use a "TODO" tag which can then b

What do you mean “%’s do not”? You mean PatternConverters? I think someone asked for that enhancement, but since the header and footer are processed before a LogEvent exists their are a whole pile of them that won’t work. Ralph On Sep 22, 2014, at 8:05 AM, Gary Gregory wrote: > On Mon, Sep

Re: [2/2] git commit: Javadoc: Replace @doubt with TODO tags. Custom @'s in Javadoc 8 are not allowed unpackaged and then must exist, and we do not have them, so just use a "TODO" tag which can then b

On Mon, Sep 22, 2014 at 10:26 AM, Ralph Goers wrote: > I thought Gary recently implemented that. > I had talked about it, and worked it out over the weekend, it's not much code actually (as expected). What was unexpected is that while lookups work in header and footers, %'s do not, so you canno

[jira] [Resolved] (LOG4J2-848) Add a Java lookup to provide nicely formatted runtime version information

[ https://issues.apache.org/jira/browse/LOG4J2-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-848. - Resolution: Fixed In master. > Add a Java lookup to provide nicely formatted runtime version info

Re: [2/2] git commit: Javadoc: Replace @doubt with TODO tags. Custom @'s in Javadoc 8 are not allowed unpackaged and then must exist, and we do not have them, so just use a "TODO" tag which can then b

I thought Gary recently implemented that. Please read the @doubts. I imagine most of them can be removed at this point. Ralph On Sep 22, 2014, at 2:29 AM, Remko Popma wrote: > I'm getting a compile error: > > Interpolator now has this line: > +lookups.put("java", new JavaLookup()); >

[jira] [Created] (LOG4J2-848) Add a Java lookup to provide nicely formatted runtime version information

Gary Gregory created LOG4J2-848: --- Summary: Add a Java lookup to provide nicely formatted runtime version information Key: LOG4J2-848 URL: https://issues.apache.org/jira/browse/LOG4J2-848 Project: Log4j

[jira] [Created] (LOG4J2-847) Allow Layout header and footer to contain % values like %d{UNIX}

Gary Gregory created LOG4J2-847: --- Summary: Allow Layout header and footer to contain % values like %d{UNIX} Key: LOG4J2-847 URL: https://issues.apache.org/jira/browse/LOG4J2-847 Project: Log4j 2

[Bug 57002] New: SocketAppender freezes for about 15 seconds if the server is not available

https://issues.apache.org/bugzilla/show_bug.cgi?id=57002 Bug ID: 57002 Summary: SocketAppender freezes for about 15 seconds if the server is not available Product: Log4j Version: 1.2.17 Hardware: PC OS: Linu

[jira] [Commented] (LOG4J2-496) Allow Layout header and footer to be configured in files and to contain properties.

[ https://issues.apache.org/jira/browse/LOG4J2-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143226#comment-14143226 ] Gary Gregory commented on LOG4J2-496: - Just to be clear, you can use a lookup like "$\

Re: git commit: Revert WIP that does not compile due to dep on the new class.

Thanks for the quick response! Sent from my iPhone > On 2014/09/22, at 20:38, [email protected] wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master ef6183cde -> 9aec5c501 > > > Revert WIP that does not compile due to dep on the new class. > > Project: http://git-w

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143185#comment-14143185 ] Remko Popma commented on LOG4J2-323: The full solution for this issue is probably to i

[jira] [Comment Edited] (LOG4J2-636) IOException: Stream Closed RollingRandomAccessFile

[ https://issues.apache.org/jira/browse/LOG4J2-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143165#comment-14143165 ] Remko Popma edited comment on LOG4J2-636 at 9/22/14 1:03 PM: -

[jira] [Resolved] (LOG4J2-636) IOException: Stream Closed RollingRandomAccessFile

[ https://issues.apache.org/jira/browse/LOG4J2-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-636. Resolution: Cannot Reproduce I initially thought this was caused by a concurrency issue but I now th

Re: [2/2] git commit: Javadoc: Replace @doubt with TODO tags. Custom @'s in Javadoc 8 are not allowed unpackaged and then must exist, and we do not have them, so just use a "TODO" tag which can then b

Arg, I was not supposed to commit that file. Will fix asap. Gary Original message From: Remko Popma Date:09/22/2014 05:29 (GMT-05:00) To: Developers List Log4J Subject: Re: [2/2] git commit: Javadoc: Replace @doubt with TODO tags. Custom @'s in Javadoc 8 are not allowed u

[jira] [Comment Edited] (LOG4J2-636) IOException: Stream Closed RollingRandomAccessFile

[ https://issues.apache.org/jira/browse/LOG4J2-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008817#comment-14008817 ] Remko Popma edited comment on LOG4J2-636 at 9/22/14 10:12 AM: --

[jira] [Closed] (LOG4J2-830) failure to shutdown JVM when join called on AsyncAppender thread

[ https://issues.apache.org/jira/browse/LOG4J2-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Honen closed LOG4J2-830. - Verified - now shuts down immediately. Thanks. > failure to shutdown JVM when join called on AsyncAppender th

[jira] [Commented] (LOG4J2-807) Disruptor is null when configuration is reloaded (asyncRoot + monitorInterval)

[ https://issues.apache.org/jira/browse/LOG4J2-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143065#comment-14143065 ] Remko Popma commented on LOG4J2-807: The problem is caused by a bug in AbstractConfigu

Re: Early Access builds for JDK 9 b31 and JDK 8u40 b06 are available on java.net

Hi Nick, We would really like to list your project along with your name as contact on the wiki at [0], is that something you would be interested in ? Rgds,Rory [0] https://wiki.openjdk.java.net/display/Adoption/Quality+Out+Reach On 22/09/2014 08:41, Rory O'Donnell Oracle, Dublin Ireland wro

Re: [2/2] git commit: Javadoc: Replace @doubt with TODO tags. Custom @'s in Javadoc 8 are not allowed unpackaged and then must exist, and we do not have them, so just use a "TODO" tag which can then b

I'm getting a compile error: Interpolator now has this line: +lookups.put("java", new JavaLookup()); But the JavaLookup class does not exist... Sent from my iPhone > On 2014/09/22, at 14:29, [email protected] wrote: > > +lookups.put("java", new JavaLookup()); ---

[jira] [Commented] (LOG4J2-506) Binary logging interface

[ https://issues.apache.org/jira/browse/LOG4J2-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143010#comment-14143010 ] Remko Popma commented on LOG4J2-506: Continuing to think out loud: For client applicat

[jira] [Comment Edited] (LOG4J2-506) Binary logging interface

[ https://issues.apache.org/jira/browse/LOG4J2-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142933#comment-14142933 ] Remko Popma edited comment on LOG4J2-506 at 9/22/14 7:46 AM: -

Early Access builds for JDK 9 b31 and JDK 8u40 b06 are available on java.net

Hi Nick, Early Access build for JDK 9 b31 is available on java.net, summary of changes are listed here Early Access build for JDK 8u40 b06 is available on java.ne