Re: [1/2] logging-log4j2 git commit: LOG4J2-1958 Deprecate SerializedLayout and remove it as default

In the manual pages, can we mention that in previous versions the default was SerializedLayout, but as of log4j-2.9 users need to explicitly specify a layout since there is no default? I think it is important to document the log4j version when this change took place. On Wed, Jun 28, 2017 at 9:52 P

Re: Release notes

Release Notes = changes.xml, no? (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 29, 2017, at 19:48, Mikael Ståldal wrote: > > Do we have any place to prepare release notes for an upcoming release, before > actually making the release? > > Removing SerializedLa

Re: Releasing 2.9

Updating the performance page with the items you mentioned is on my todo list but I doubt I'll be able to get to it in July or even August. Performance testing, analyzing the results, redoing after finding I measured the wrong thing:-) and finally doing a write up of the results took me several we

Re: [Log4j] 2.9 release and Java 9

Not sure I agree. Our interest in Android is a very recent thing. We've done some work with LOG4J2-1926 , we are still discovering new work and I suspect we will keep discovering new issues as we start to take an in-depth look. If anything, let's m

Re: [Log4j] 2.9 release and Java 9

* When I said "Java 9 has been on the roadmap" I meant the Log4j 2 roadmap. On Sun, Jul 9, 2017 at 9:15 PM, Remko Popma wrote: > Not sure I agree. Our interest in Android is a very recent thing. We've > done some work with LOG4J2-1926 > <https://issues.apache.org/j

Re: [Log4j] 2.9 release and Java 9

One problem with the log4j-api-android idea is that it doesn't cover other libraries that bring in a dependency to log4j-api. However, I wouldn't mind saying Log4j 2.9 supports Java 9 but not Android; on Android use Log4j 2.8. (Shameless plug) Every java main() method deserves http://picocli.inf

Re: [Log4j] 2.9 release and Java 9

I think both Gary and myself had the same misunderstanding about log4j-api-android. I didn't realize it contains a bridge/adapter to the Android logging implementation until you mentioned it. Would `log4j-api-android-impl` be a better name? (Shameless plug) Every java main() method deserves ht

Re: [JIRA] Editing comments

Reopen the issue. Once the issue is closed, you can only add comments, not edit them. (Shameless plug) Every java main() method deserves http://picocli.info > On Jul 15, 2017, at 4:31, Gary Gregory wrote: > > Hi All, > > What do we have to do to allow us to EDIT comments? > > Gary > Typo Ma

Re: Build failed in Jenkins: Log4j 2.x #2907

I think compilation fails because the class version is incompatible: we're using the 1.7 javac to compile but use the 1.8 jconsole jar as a compilation dependency. (Shameless plug) Every java main() method deserves http://picocli.info > On Jul 18, 2017, at 15:26, Gary Gregory wrote: > > Beca

Re: Left to do for 2.9 release

> On Jul 31, 2017, at 5:59, Gary Gregory wrote: > > On Sun, Jul 30, 2017 at 1:48 PM, Gary Gregory > wrote: > >> * I think the new logic to avoid logging calls blowing up ( >> ConcurrentModificationException) circumvents the ignoreExceptions >> settings on appenders. >> > > If wonder if we sh

picocli in log4j

Thanks all for your positive feedback on picocli back in April. There have been multiple releases since then and I am confident about its stability now. Any objections if I replace our current usage of JCommander with picocli? Main benefits: - C

Re: [VOTE] Release log4cxx 1.1.0

+1 Remko On Wed, May 3, 2023 at 2:34 AM Thorsten Schöning wrote: > Guten Tag Robert Middleton, > am Dienstag, 2. Mai 2023 um 13:47 schrieben Sie: > > > Please download, test, and cast your votes on the log4j developers list. > > [] +1, release the artifacts > > [] -1, don't release because... >

Re: Optional dependencies in `log4j-core` 3.x

> 1. Configuration has properties related to async logging: `asyncLoggerConfigDelegate` and `asyncWaitStrategyFactory`. These should be removed before the split, but I don't know what would be the right way to do it. How would that work? Will Log4j 3 configurations be incompatible with Log4j 2 con

Re: [VOTE] Release Apache Log4j JMX GUI 2.21.0

+1 Remko > On Sep 14, 2023, at 16:34, Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j JMX GUI 2.21.0. > > Source repository: https://github.com/apache/logging-log4j-jmx-gui > Commit: 35d3021e995393a0f62198c2c65af8b47e42688b > Distribution: https://dist.apache.org/repos/

Re: Refining product feature set strategy

+1 to what Ralph said On Sat, Sep 30, 2023 at 0:56 Scott Deboy wrote: > +1 to everything Ralph said. > > On Fri, Sep 29, 2023, 3:53 PM Ralph Goers > wrote: > > > I’m sorry, I can’t really agree with much of any of this. Following the > > thoughts being proposed in this thread much of Log4j 2 an

Re: Change semantics of `Throwable` parameters

> On Nov 23, 2023, at 18:31, Piotr P. Karwasz wrote: > > Hi Matt, > >> On Tue, 21 Nov 2023 at 23:22, Matt Sicker wrote: >> >> This sounds like it might be a good basis for figuring out a parallel v3 API >> for a “hard to mis-use” style API. However, once you go that route, you >> start to

Re: [log4j] Performance figures

I’m open to improvements in this area. Before going into details or specifics though, I’m curious: What do we (users, developers and PMC members) consider to be the “value proposition” of Log4j? Why should people choose Log4j over the alternatives? This is a positioning question; what are the

interesting writeup of some nice engineering

https://www.uber.com/en-JP/blog/reducing-logging-cost-by-two-orders-of-magnitude-using-clp/ tldr: Uber created a CLP appender for log4j that compresses on the fly. Impressive 169x compression rate. Resulting compressed

Re: New committer: Fred am Nil (`freeandnil`)

Welcome Fred / Jan. I like your email handle freeandnil. :-) Welcome aboard! -Remko On Sat, Feb 10, 2024 at 4:54 AM Fred am Nil wrote: > Hello, > > thank you very much for the warm welcome. > I'm looking forward to collaborating with everyone and making meaningful > contributions to the Apache L

Re: Video Call on June 2, 2024

I appreciate the update and the summary. Thanks all. > On Jun 3, 2024, at 22:55, Ralph Goers wrote: > > Several of the PMC members met yesterday to primarily discuss the > ScopedContext and getting release 2.24.0 ready. The notes from that meeting > are at > https://docs.google.com/documen

Re: Compatibility between Log4j API and implementation

I agree with Gary. That is a good reason to release every module with every release, to save people the headache of figuring out compatible versions. On Thu, Nov 14, 2024 at 9:41 PM Gary Gregory wrote: > I think you keep it simple: versions must match. > > Versions that are unmatched are not sup

Re: New committer: Jay Katariya

Welcome Jay! > On Jan 23, 2025, at 5:55, Jay Kataria wrote: > > Hello Everyone, > > My name is Jay, I have always wanted to contribute to Open Source and > finally am realizing that dream through the logging project. Hopefully I am > able to contribute and work a lot in the project 🙂 > > Rega

Re: Question: "Garbage-Free" AbstractFilter#filter(...) methods.

Garbage free is mostly about predictable latency. In my work we create trading applications that send orders to the stock exchange when market conditions change. If the JVM would decide to stop the world to collect garbage, we might not get the orders sent out in time. Our whole stack (messag

[jira] [Created] (LOG4J2-2011) replace JCommander with picocli

Remko Popma created LOG4J2-2011: --- Summary: replace JCommander with picocli Key: LOG4J2-2011 URL: https://issues.apache.org/jira/browse/LOG4J2-2011 Project: Log4j 2 Issue Type: Improvement

[jira] [Resolved] (LOG4J2-2011) replace JCommander with picocli

[ https://issues.apache.org/jira/browse/LOG4J2-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-2011. - Resolution: Fixed Migrated to picocli, and users no longer need an external dependency to run

[jira] [Updated] (LOG4J2-2011) replace JCommander with picocli

[ https://issues.apache.org/jira/browse/LOG4J2-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2011: Description: As discussed in the mailing list, replace uses of JCommander with [picocli|https

[jira] [Created] (LOG4J2-2018) LoggerNameLevelRewritePolicy documentation is wrong, example is broken

Remko Popma created LOG4J2-2018: --- Summary: LoggerNameLevelRewritePolicy documentation is wrong, example is broken Key: LOG4J2-2018 URL: https://issues.apache.org/jira/browse/LOG4J2-2018 Project: Log4j

[jira] [Closed] (LOG4J2-2018) LoggerNameLevelRewritePolicy documentation is wrong, example is broken

[ https://issues.apache.org/jira/browse/LOG4J2-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-2018. --- Resolution: Fixed Fixed the docs rather than the implementation. > LoggerNameLevelRewritePol

[jira] [Commented] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

[ https://issues.apache.org/jira/browse/LOG4J2-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129555#comment-16129555 ] Remko Popma commented on LOG4J2-2019: - Interesting question. A simple progra

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131541#comment-16131541 ] Remko Popma commented on LOG4J2-1896: - So, essentially, the reconnect use

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135981#comment-16135981 ] Remko Popma commented on LOG4J2-2023: - As discussed in the mailing list, the

[jira] [Assigned] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1896: --- Assignee: Remko Popma (was: Gary Gregory) > Update classes

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151243#comment-16151243 ] Remko Popma commented on LOG4J2-1896: - Okay, I will take a look at this. >

[jira] [Commented] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153768#comment-16153768 ] Remko Popma commented on LOG4J2-2031: - I haven't looked in great detail,

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153768#comment-16153768 ] Remko Popma edited comment on LOG4J2-2031 at 9/5/17 3:0

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153768#comment-16153768 ] Remko Popma edited comment on LOG4J2-2031 at 9/5/17 3:2

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153768#comment-16153768 ] Remko Popma edited comment on LOG4J2-2031 at 9/5/17 3:2

[jira] [Commented] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158590#comment-16158590 ] Remko Popma commented on LOG4J2-2031: - I think I know what is happening with

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158590#comment-16158590 ] Remko Popma edited comment on LOG4J2-2031 at 9/8/17 1:0

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158590#comment-16158590 ] Remko Popma edited comment on LOG4J2-2031 at 9/8/17 1:2

[jira] [Updated] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2031: Summary: Messages appear out of order in log file (was: Log4j2 log file not reflecting application

[jira] [Assigned] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-2031: --- Assignee: Remko Popma > Messages appear out of order in log file (was: Log4j2 log file

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160342#comment-16160342 ] Remko Popma commented on LOG4J2-2031: - After thinking about this some more, I t

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161078#comment-16161078 ] Remko Popma commented on LOG4J2-2041: - [~william_f_au] It it possible to run j

[jira] [Assigned] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-2035: --- Assignee: Remko Popma > There is no such lib as disruptor-3.

[jira] [Commented] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161096#comment-16161096 ] Remko Popma commented on LOG4J2-2035: - I looked at the LMAX Disruptor Changelog

[jira] [Assigned] (LOG4J2-1914) AsyncLogger and message formatting (ConcurrentModificationException)

[ https://issues.apache.org/jira/browse/LOG4J2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1914: --- Assignee: Remko Popma > AsyncLogger and message formatting (ConcurrentModificationExcept

[jira] [Commented] (LOG4J2-1988) java.util.ConcurrentModificationException with AsyncLogger?

[ https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161245#comment-16161245 ] Remko Popma commented on LOG4J2-1988: - The stack trace shows that the log e

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161292#comment-16161292 ] Remko Popma commented on LOG4J2-2041: - It just looked weird to me that one woul

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162158#comment-16162158 ] Remko Popma commented on LOG4J2-2031: - Hi Colin,

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162169#comment-16162169 ] Remko Popma commented on LOG4J2-2031: - Thanks for pointing out that

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162175#comment-16162175 ] Remko Popma commented on LOG4J2-2041: - Thanks for trying, Ralph! > 2.9.0 c

[jira] [Created] (LOG4J2-2048) Increase default queue size for AsyncAppender

Remko Popma created LOG4J2-2048: --- Summary: Increase default queue size for AsyncAppender Key: LOG4J2-2048 URL: https://issues.apache.org/jira/browse/LOG4J2-2048 Project: Log4j 2 Issue Type

[jira] [Resolved] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-2035. - Resolution: Fixed Fix Version/s: 2.9.1 Fixed in master. Please verify and close. > Th

[jira] [Resolved] (LOG4J2-2048) Increase default queue size for AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-2048. - Resolution: Fixed Fixed in master. > Increase default queue size for AsyncAppen

[jira] [Closed] (LOG4J2-2048) Increase default queue size for AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-2048. --- > Increase default queue size for AsyncAppen

[jira] [Commented] (LOG4J2-2050) NullPointerException in LogManager.getLogger when called from anonymous class initializer

[ https://issues.apache.org/jira/browse/LOG4J2-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165894#comment-16165894 ] Remko Popma commented on LOG4J2-2050: - Thanks Matt, I was looking for snap

[jira] [Updated] (LOG4J2-1988) java.util.ConcurrentModificationException with AsyncLogger?

[ https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1988: Priority: Major (was: Minor) > java.util.ConcurrentModificationException with AsyncLog

[jira] [Resolved] (LOG4J2-1988) java.util.ConcurrentModificationException with AsyncLogger?

[ https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1988. - Resolution: Fixed Fix Version/s: 2.9.1 Fixed in master. I was able to add a test that

[jira] [Resolved] (LOG4J2-1914) AsyncLogger and message formatting (ConcurrentModificationException)

[ https://issues.apache.org/jira/browse/LOG4J2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1914. - Resolution: Fixed Fix Version/s: 2.9.1 Fixed in master. I was able to add a test that

[jira] [Comment Edited] (LOG4J2-1988) java.util.ConcurrentModificationException with AsyncLogger?

[ https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168059#comment-16168059 ] Remko Popma edited comment on LOG4J2-1988 at 9/15/17 3:5

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168210#comment-16168210 ] Remko Popma commented on LOG4J2-2052: - I wasn't aware of that fix. We cou

[jira] [Comment Edited] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168210#comment-16168210 ] Remko Popma edited comment on LOG4J2-2052 at 9/15/17 5:1

[jira] [Commented] (LOG4J2-2051) Update Conversant Disruptor from 1.2.10 to 1.2.11.

[ https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168821#comment-16168821 ] Remko Popma commented on LOG4J2-2051: - Should we leave this ticket open, or res

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169468#comment-16169468 ] Remko Popma commented on LOG4J2-2052: - I would prefer to keep the default as is,

[jira] [Assigned] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-2052: --- Assignee: Remko Popma > Disable thread name caching by defa

[jira] [Updated] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2031: Fix Version/s: 2.10.0 > Messages appear out of order in log file (was: Log4j2 log file

[jira] [Updated] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2031: Affects Version/s: 2.9.1 > Messages appear out of order in log file (was: Log4j2 log file

[jira] [Resolved] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-2031. - Resolution: Fixed Fixed in master. Please verify and close. > Messages appear out of order

[jira] [Comment Edited] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173217#comment-16173217 ] Remko Popma edited comment on LOG4J2-2031 at 9/20/17 3:4

[jira] [Commented] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176087#comment-16176087 ] Remko Popma commented on LOG4J2-2035: - >From Log4j 2.9, async loggers now

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177466#comment-16177466 ] Remko Popma commented on LOG4J2-2052: - Actually I just realized this can b

[jira] [Updated] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1896: Fix Version/s: (was: 2.9.1) 2.10.0 > Update classes

[jira] [Created] (LOG4J2-2054) Provide alternative to configuring SecureSocketAppender to avoid plain-text passwords in config

Remko Popma created LOG4J2-2054: --- Summary: Provide alternative to configuring SecureSocketAppender to avoid plain-text passwords in config Key: LOG4J2-2054 URL: https://issues.apache.org/jira/browse/LOG4J2-2054

[jira] [Updated] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2054: Summary: Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177901#comment-16177901 ] Remko Popma commented on LOG4J2-2054: - That is certainly another option. I hav

[jira] [Resolved] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1896. - Resolution: Fixed The various StoreConfiguration classes now get a reference to a

[jira] [Comment Edited] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177908#comment-16177908 ] Remko Popma edited comment on LOG4J2-1896 at 9/23/17 5:4

[jira] [Reopened] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1896: - As per discussion in LOG4J2-2054, I will replace the {{PasswordProvider}} interface with a generic

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178019#comment-16178019 ] Remko Popma commented on LOG4J2-2054: - Thanks for the good feedback! I've

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178121#comment-16178121 ] Remko Popma commented on LOG4J2-2056: - Is it a good idea to use the below? |l

[jira] [Resolved] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-2052. - Resolution: Fixed Fix Version/s: 2.10.0 Fixed in master. Please verify and close

[jira] [Updated] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2054: Summary: Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[jira] [Updated] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2054: Description: Following up on LOG4J2-1896, currently SecureSocketAppender can only be configured

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178460#comment-16178460 ] Remko Popma commented on LOG4J2-1896: - (Note to self, still looking into

[jira] [Closed] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-2054. --- Resolution: Fixed > Provide ways to configure SSL that avoid plain-text passwords in the lo

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180775#comment-16180775 ] Remko Popma commented on LOG4J2-1896: - The most general interface for SSL seem

[jira] [Comment Edited] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180775#comment-16180775 ] Remko Popma edited comment on LOG4J2-1896 at 9/26/17 2:0

[jira] [Created] (LOG4J2-2059) Refactor classes in core.net.ssl to allow non-KeyStore Providers

Remko Popma created LOG4J2-2059: --- Summary: Refactor classes in core.net.ssl to allow non-KeyStore Providers Key: LOG4J2-2059 URL: https://issues.apache.org/jira/browse/LOG4J2-2059 Project: Log4j 2

[jira] [Resolved] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1896. - Resolution: Fixed I created a separate ticket LOG4J2-2059 to deal with non-KeyStore based

[jira] [Updated] (LOG4J2-2059) Refactor classes in core.net.ssl to allow non-KeyStore Providers

[ https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2059: Priority: Minor (was: Major) > Refactor classes in core.net.ssl to allow non-KeyStore Provid

[jira] [Updated] (LOG4J2-2059) Refactor classes in core.net.ssl to allow non-KeyStore Providers

[ https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2059: Description: Refactor classes in the core.net.ssl package so that an SSL context can be created

[jira] [Updated] (LOG4J2-2059) Refactor classes in core.net.ssl to allow non-KeyStore Providers

[ https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2059: Description: Refactor classes in the core.net.ssl package so that an SSL context can be created

[jira] [Commented] (LOG4J2-1479) Help Apache Spark project to upgrade from Log4j 1.x to 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189914#comment-16189914 ] Remko Popma commented on LOG4J2-1479: - If people are looking to help out, the

[jira] [Assigned] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-2060: --- Assignee: Remko Popma > AbstactDatabase appender issue with AsyncLog

[jira] [Updated] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2060: Fix Version/s: 2.9.2 > AbstactDatabase appender issue with AsyncLog

[jira] [Commented] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193245#comment-16193245 ] Remko Popma commented on LOG4J2-2060: - You are correct. AbstractDatabaseMan

[jira] [Commented] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197066#comment-16197066 ] Remko Popma commented on LOG4J2-2060: - Glad you were able to confirm that

[jira] [Commented] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205113#comment-16205113 ] Remko Popma commented on LOG4J2-2060: - I've committed a fix to master. It

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968431#comment-15968431 ] Remko Popma commented on LOG4J2-1883: - Is this about microsecond time or the

<    1   2   3   4   5   6   >