Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

ave it continue with the current > behavior. > > Sent from my iPhone > >> On Apr 11, 2017, at 5:47 PM, Remko Popma <remko.po...@gmail.com> wrote: >> >> I can see both sides of the argument. >> >> Rather than changing the semantics of the existing method, what

Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

I can see both sides of the argument. Rather than changing the semantics of the existing method, what about adding a method `Configurator.initializeStrict(String, String)` which fails if the specified file doesn't exist? Not sure what the best way to fail is: return null or throw exception...

Re: Configuration file discovery

A better error message sounds like a good idea. If you make a Jira ticket for this, please make it part of the "ergonomics" epic: https://issues.apache.org/jira/browse/LOG4J2-1811 On Tue, Apr 11, 2017 at 9:19 PM, Mikael Ståldal wrote: > Some configuration file formats

Re: [14/14] logging-log4j2 git commit: Update BOM

;> >>>> On Mon, Apr 10, 2017 at 5:48 PM, Ralph Goers <ralph.go...@dslextreme.com> >>>> wrote: >>>> I created a new git repo for log4j2-tools. We should not create any more >>>> modules if we can avoid it. >>>> >>>

Re: [14/14] logging-log4j2 git commit: Update BOM

or server and another for the other > tools? > > On Mon, Apr 10, 2017 at 4:23 PM, Remko Popma <remko.po...@gmail.com> > wrote: > >> I thought we were going to name this module log4j-tools instead of >> log4j-server, so it can host all our standalone apps? &

Re: [14/14] logging-log4j2 git commit: Update BOM

I thought we were going to name this module log4j-tools instead of log4j-server, so it can host all our standalone apps? On Mon, Apr 10, 2017 at 11:11 PM, wrote: > Update BOM > > > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo > Commit:

[jira] [Commented] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

[ https://issues.apache.org/jira/browse/LOG4J2-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962607#comment-15962607 ] Remko Popma commented on LOG4J2-1873: - I'm open to ideas. We did something similar

Re: [ANN] Log4j 2.8.2 released

Blogged: https://blogs.apache.org/logging/entry/log4j-2-8-2-released On Sun, Apr 9, 2017 at 1:53 AM, Matt Sicker wrote: > The Apache Log4j 2 team is pleased to announce the Log4j 2.8.2 release! > > Apache Log4j is a well known framework for logging application behavior. >

Re: Yet another logging facade

Good find. I noticed that the document points to Apache Sling and says "uses the most common parts today used for logging: SLF4J for clients and logback for processing." Seems like Sling decided that in 2013 and never looked back. Which is fine, but I believe Log4j2 has changed the landscape

Re: MessageLayout

So, exceptions are swallowed and no newlines are rendered? Interesting. What's the use case? Sent from my iPhone > On Apr 4, 2017, at 7:30, Gary Gregory wrote: > > Hi All, > > I am considering a new layout called "MessageLayout" which would be > synonymous with:.

[jira] [Commented] (LOG4J2-1857) Listing all Loggers via JMX

[ https://issues.apache.org/jira/browse/LOG4J2-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942847#comment-15942847 ] Remko Popma commented on LOG4J2-1857: - Yes, good idea. I am swamped with other work. Can you provide

[jira] [Comment Edited] (LOG4J2-1857) Listing all Loggers via JMX

[ https://issues.apache.org/jira/browse/LOG4J2-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942847#comment-15942847 ] Remko Popma edited comment on LOG4J2-1857 at 3/27/17 8:41 AM: -- Yes, good

[jira] [Comment Edited] (LOG4J2-1857) Listing all Loggers via JMX

[ https://issues.apache.org/jira/browse/LOG4J2-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942265#comment-15942265 ] Remko Popma edited comment on LOG4J2-1857 at 3/26/17 12:57 PM: --- Does

[jira] [Updated] (LOG4J2-1857) Listing all Loggers via JMX

[ https://issues.apache.org/jira/browse/LOG4J2-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1857: Description: How can I list all loggers via JMX / jolokia? (was: Who I can list all logger via

[jira] [Commented] (LOG4J2-1857) List all Loger via JMx

[ https://issues.apache.org/jira/browse/LOG4J2-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942265#comment-15942265 ] Remko Popma commented on LOG4J2-1857: - Does this work for you? {code} String serviceUrl

[jira] [Closed] (LOG4J2-1370) Log4j2 cannot get env. variable

[ https://issues.apache.org/jira/browse/LOG4J2-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1370. --- Resolution: Resolved User reported that a they could not reproduce the issue any more after

[jira] [Resolved] (LOG4J2-1849) Broken FixedDateFormat tests when daylight saving time starts

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

Re: Java 9 support

Sorry, no idea. A separate repo sounds cleaner, but I haven't spent as much time as you thinking about this, so perhaps I'm wrong. It would be nice to not require Java 9 unless you want to compile the StackWalker stuff... On Thu, Mar 16, 2017 at 12:07 AM, Ralph Goers

[jira] [Updated] (LOG4J2-1841) Problems with consequences after LOG4J2-248

[ https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1841: Fix Version/s: 2.8.2 Setting fix version to prevent this issue from dropping below the horizon

[jira] [Commented] (LOG4J2-1849) Broken FixedDateFormat tests when daylight saving time starts

[ https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926127#comment-15926127 ] Remko Popma commented on LOG4J2-1849: - Thanks for the test. I will need to modify it slightly because

[jira] [Commented] (LOG4J2-1849) Broken FixedDateFormat tests when daylight saving time starts

[ https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924232#comment-15924232 ] Remko Popma commented on LOG4J2-1849: - I've started to look at this. The idea of FixedDateFormat

[jira] [Assigned] (LOG4J2-1849) Broken FixedDateFormat tests when daylight saving time starts

[ https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1849: --- Assignee: Remko Popma > Broken FixedDateFormat tests when daylight saving time sta

[jira] [Comment Edited] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906209#comment-15906209 ] Remko Popma edited comment on LOG4J2-1359 at 3/11/17 2:09 PM

[jira] [Comment Edited] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906209#comment-15906209 ] Remko Popma edited comment on LOG4J2-1359 at 3/11/17 2:05 PM

[jira] [Commented] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906209#comment-15906209 ] Remko Popma commented on LOG4J2-1359: - Is it possible to compile only one class with Java 9

[jira] [Comment Edited] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905468#comment-15905468 ] Remko Popma edited comment on LOG4J2-1844 at 3/10/17 5:46 PM: -- I believe

[jira] [Resolved] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1844. - Resolution: Not A Problem I believe the specified pattern is wrong and should be {{ %d\{-MM

[jira] [Updated] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1844: Description: if pattern contains Month like {{%d\{-mm-dd HH:mm:ss.SSS\}}} log has wrong Month

[jira] [Assigned] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1844: --- Assignee: Remko Popma > Not the correct value of the month in the

[jira] [Commented] (LOG4J2-1841) Problems with consequences after LOG4J2-248

[ https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903193#comment-15903193 ] Remko Popma commented on LOG4J2-1841: - Sounds like we should roll back LOG4J2-248. Matt, what do you

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> d...@logging.apache.org +1 log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@ -> u...@logging.apache.org Interesting discussion. I can see both pros and cons. How will this work for users currently subscribed to

Re: Roadmap for 2.8.1

releases of Log4j 2 and log4j-scala should be >>> independent in both ways, right? >>> >>> I think I have coordination between log4j-scala and Scala language covered >>> already. >>> >>>> On Fri, Mar 3, 2017 at 10:19 AM, Remko Popma <r

Re: Performance page for next release.

ydgreg...@gmail.com> wrote: > > I think we should keep the current doc pages on the site perhaps under a > different heading. This would be interesting for people who cannot keep up > with the latest. > > Gary > >> On Fri, Mar 3, 2017 at 1:20 PM, Remko Popma <remko.po...@gm

Re: Performance page for next release.

t; >> On Mar 3, 2017, at 2:20 PM, Remko Popma <remko.po...@gmail.com> wrote: >> >> Yes but only the JMH benchmarks. Is that acceptable? >> >> The latency tests and the non-JMH Async Logger tests are too involved... >> >> One thing to bear in

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895092#comment-15895092 ] Remko Popma commented on LOG4J2-1259: - Do you want to provide a patch for the Log4j2 manual? > Lo

Re: Performance page for next release.

Yes but only the JMH benchmarks. Is that acceptable? The latency tests and the non-JMH Async Logger tests are too involved... One thing to bear in mind, we carefully documented the versions of the libraries we compared against with our benchmark results. The fact that newer versions of these

Re: Roadmap for 2.8.1

gt;>> >>>>>>>> On Tue, Feb 28, 2017 at 4:08 PM, Matt Sicker <boa...@gmail.com> wrote: >>>>>>>> One issue we came across in practice is that Scala 2.12 requires Java >>>>>>>> 8, but we don't want to require that

Re: [ANNOUNCEMENT] Apache Log4j 2.8.1 released

Blogged: https://blogs.apache.org/logging/entry/log4j-2-8-1-released On Fri, Mar 3, 2017 at 2:27 PM, Ralph Goers wrote: > The Apache Log4j 2 team is pleased to announce the Log4j 2.8.1 release! > > Apache Log4j is a well known framework for logging application

[jira] [Comment Edited] (LOG4J2-1761) Support for standard java queues for the async logger

[ https://issues.apache.org/jira/browse/LOG4J2-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891237#comment-15891237 ] Remko Popma edited comment on LOG4J2-1761 at 3/1/17 10:58 PM: -- You can get

[jira] [Commented] (LOG4J2-1761) Support for standard java queues for the async logger

[ https://issues.apache.org/jira/browse/LOG4J2-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891237#comment-15891237 ] Remko Popma commented on LOG4J2-1761: - You can get some of the advantages by using AsyncAppender. You

Re: [VOTE] Release Log4j 2.8.1-rc1

Darn, we'll miss each other by 18 hours. Almost indeed! Sent from my iPhone > On Mar 1, 2017, at 20:32, Gary Gregory <garydgreg...@gmail.com> wrote: > > I land at AMS on March 5 9 AM. Almost! > > Gary > >> On Tue, Feb 28, 2017 at 11:28 PM, Remko Popma

Re: [VOTE] Release Log4j 2.8.1-rc1

+1 Sent from my iPhone > On Feb 27, 2017, at 3:09, Ralph Goers wrote: > > This is a vote to release Log4j 2.8.1 the next version of the Log4j 2 project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > []

[jira] [Commented] (LOG4J2-1829) Delete log files older than x days and max size of a log file should be y(MB)

[ https://issues.apache.org/jira/browse/LOG4J2-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889858#comment-15889858 ] Remko Popma commented on LOG4J2-1829: - Have you seen the Custom Delete action supported

Re: [VOTE] Release Log4j 2.8.1-rc1

person! Are you in Europe now? > > Gary > > On Mon, Feb 27, 2017 at 11:36 PM, Remko Popma <remko.po...@gmail.com> > wrote: > >> FYI I won't be able to start reviewing until Wednesday (likely evening >> Amsterdam time). >> >> On Mon, Feb 27,

Re: Roadmap for 2.8.1

To be honest I still don't understand * the vision of what we ultimately want to achieve * how different repos fit into that vision * what different websites we are planning to create to give users access to these different modules * what websites are going to be driven from which modules or

Re: [VOTE] Release Log4j 2.8.1-rc1

FYI I won't be able to start reviewing until Wednesday (likely evening Amsterdam time). On Mon, Feb 27, 2017 at 3:09 Ralph Goers wrote: > This is a vote to release Log4j 2.8.1 the next version of the Log4j 2 > project. > > Please download, test, and cast your votes

Re: Does ByteBufferDestination.drain() even need an argument?

code doesn't have a need for complicated > layouts, but ensuring the write buffer has enough space between each and > every byte would be extremely tedious). > > On 26 February 2017 at 19:48, Remko Popma <remko.po...@gmail.com> wrote: > > Similarly to the way the drain() method giv

Re: Does ByteBufferDestination.drain() even need an argument?

Similarly to the way the drain() method gives *implementations *the flexibility to return a different ByteBuffer, I wanted to also give *callers *the flexibility to drain a different ByteBuffer. I don't have a concrete use case for it, but I imagined there might be cases where callers overflowed

Re: Release Notes

Afonso Murakami, if you are a chatbot please unsubscribe. You are failing the Turing test. Guys, I suspect someone is trying to train their chatbot on our mailing list... If this continues we may need to unsubscribe it ourselves... On Mon, Feb 27, 2017 at 10:25 AM, Matt Sicker

Re: Experimenting with NIO

Afonso, are you a robot? On Mon, Feb 27, 2017 at 8:44 AM, Afonso Murakami wrote: > That is great thank you very much for your help > > On Feb 26, 2017, at 3:36 PM, Matt Sicker wrote: > > Afonso, are you on the right mailing list? > > Anyways, I've made

[jira] [Commented] (LOG4J2-1797) Add asynchronous/non-blocking SPIs for appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884093#comment-15884093 ] Remko Popma commented on LOG4J2-1797: - Would it be possible to use the LMAX ExceptionHandler

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884087#comment-15884087 ] Remko Popma commented on LOG4J2-1807: - Looking at the code, I would suggest: * removing the non

Re: Undeprecating MessageSupplier

Thanks Matt! On Sat, Feb 25, 2017 at 2:47 PM, Matt Sicker <boa...@gmail.com> wrote: > Changed in https://issues.apache.org/jira/browse/LOG4J2-1823 > > On 24 February 2017 at 12:58, Remko Popma <remko.po...@gmail.com> wrote: > >> +1 I'm fine with undeprecatin

Re: Undeprecating MessageSupplier

+1 I'm fine with undeprecating MessageSupplier. Remko Sent from my iPhone > On Feb 24, 2017, at 19:07, Matt Sicker wrote: > > In log4j-api, the interface MessageSupplier has been deprecated ever since we > realized that we didn't need it and could just use Supplier for >

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876449#comment-15876449 ] Remko Popma commented on LOG4J2-1820: - Hi Jason, I'm traveling and may not get around to looking

[jira] [Updated] (LOG4J2-1760) AsyncAppender with LinkedTransferQueue.offer()

[ https://issues.apache.org/jira/browse/LOG4J2-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1760: Fix Version/s: 2.8.1 > AsyncAppender with LinkedTransferQueue.of

[jira] [Assigned] (LOG4J2-1760) AsyncAppender with LinkedTransferQueue.offer()

[ https://issues.apache.org/jira/browse/LOG4J2-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1760: --- Assignee: Remko Popma > AsyncAppender with LinkedTransferQueue.of

[jira] [Commented] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872993#comment-15872993 ] Remko Popma commented on LOG4J2-1563: - I Saw you raised LOG4J2-1820 for the new issue. Perfect

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872545#comment-15872545 ] Remko Popma commented on LOG4J2-1807: - They have different usages. From memory: the Builder is used

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871191#comment-15871191 ] Remko Popma commented on LOG4J2-1807: - Gary, will do. I'll try to make time in the next few weeks

Re: Async logging and thread name

Hi Leon, Yes by default the thread name is cached. There is a system property to switch that off: see https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/async/ThreadNameCachingStrategy.java The reason for the caching is that every call

Re: RollingAppenderSizeTest failures

The new test failure (can't open zip) looks like a one-off... Sent from my iPhone > On Feb 15, 2017, at 9:58, Gary Gregory wrote: > >> On Tue, Feb 14, 2017 at 3:22 PM, Apache wrote: >> What problem before what? >> >> RollingAppenderSizeTest

[jira] [Closed] (LOG4J2-1816) Fix minOccur in log4j-config.xsd

[ https://issues.apache.org/jira/browse/LOG4J2-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1816. --- Resolution: Fixed Pull request accepted in commit 2cb9949. Keep 'em coming! > Fix minOccur in lo

[jira] [Created] (LOG4J2-1816) Fix minOccur in log4j-config.xsd

Remko Popma created LOG4J2-1816: --- Summary: Fix minOccur in log4j-config.xsd Key: LOG4J2-1816 URL: https://issues.apache.org/jira/browse/LOG4J2-1816 Project: Log4j 2 Issue Type: Bug Affects

[jira] [Commented] (LOG4J2-1814) Wrapper Generate$ExtendedLogger name inconvenient on Linux

[ https://issues.apache.org/jira/browse/LOG4J2-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865220#comment-15865220 ] Remko Popma commented on LOG4J2-1814: - That is what I had in mind. Sorry I wasn't clear. > Wrap

[jira] [Commented] (LOG4J2-1814) Wrapper Generate$ExtendedLogger name inconvenient on Linux

[ https://issues.apache.org/jira/browse/LOG4J2-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865065#comment-15865065 ] Remko Popma commented on LOG4J2-1814: - Also, improve the docs to clarify usage (http

[jira] [Updated] (LOG4J2-1814) Wrapper Generate$ExtendedLogger name inconvenient on Linux

[ https://issues.apache.org/jira/browse/LOG4J2-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1814: Description: The $ExtendedLogger is interpreted as an environment variable. {code} $ java -cp

[jira] [Updated] (LOG4J2-1814) Wrapper Generate$ExtendedLogger name inconvenient on Linux

[ https://issues.apache.org/jira/browse/LOG4J2-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1814: Description: The $ExtendedLogger is interpreted as an environment variable. {code} $ java -cp

[jira] [Updated] (LOG4J2-1814) Wrapper Generate$ExtendedLogger name inconvenient on Linux

[ https://issues.apache.org/jira/browse/LOG4J2-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1814: External issue URL: https://gist.github.com/sdwsk/47b86d243023b1583d340889a89639f6 > Wrap

[jira] [Created] (LOG4J2-1814) Wrapper Generate$ExtendedLogger name inconvenient on Linux

Remko Popma created LOG4J2-1814: --- Summary: Wrapper Generate$ExtendedLogger name inconvenient on Linux Key: LOG4J2-1814 URL: https://issues.apache.org/jira/browse/LOG4J2-1814 Project: Log4j 2

[jira] [Commented] (LOG4J2-1808) java.lang.NoSuchMethodError: org.apache.logging.log4j.ThreadContext.getThreadContextMap()

[ https://issues.apache.org/jira/browse/LOG4J2-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863818#comment-15863818 ] Remko Popma commented on LOG4J2-1808: - Glad to hear that. > java.lang.NoSuchMethodEr

[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

Re: Logback performance improvements

#FriendsDontLetFriendsUseJavaUtilLogging On Sun, Feb 12, 2017 at 11:41 PM, Remko Popma <remko.po...@gmail.com> 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 > appe

Re: Logback performance improvements

more. We did document that <https://logging.apache.org/log4j/2.x/performance.html#fileLoggingComparison> but perhaps we need to evangelize it more... On Sun, Feb 12, 2017 at 4:59 PM, Remko Popma <remko.po...@gmail.com> wrote: > The queue is bigger but still fills up quic

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

full. I also don’t understand why AsyncLogger is > slower as it should have a large ring buffer if I understand correctly. > > Ralph > >> On Feb 11, 2017, at 4:36 PM, Remko Popma <remko.po...@gmail.com> wrote: >> >> I don't think it is a good idea to

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

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862663#comment-15862663 ] Remko Popma edited comment on LOG4J2-1811 at 2/12/17 6:00 AM: -- I agree

[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=15862663#comment-15862663 ] Remko Popma commented on LOG4J2-1811: - I agree our documentation is very good and certainly thorough

[jira] [Updated] (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:all-tabpanel ] Remko Popma updated LOG4J2-1813: Description: People find it difficult to troubleshoot Log4j 2 configuration issues. Many people

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

Remko Popma created LOG4J2-1813: --- Summary: Provide shorter and more intuitive way to switch on Log4j internal debug logging Key: LOG4J2-1813 URL: https://issues.apache.org/jira/browse/LOG4J2-1813

[jira] [Updated] (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:all-tabpanel ] Remko Popma updated LOG4J2-1812: Description: When configuration fails because no Log4j 2 configuration file is found

[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=15862652#comment-15862652 ] Remko Popma commented on LOG4J2-1812: - Added above text to the error message in commit 2467ef5

[jira] [Created] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

Remko Popma created LOG4J2-1812: --- Summary: Improve error message when log4j 2 configuration file not found Key: LOG4J2-1812 URL: https://issues.apache.org/jira/browse/LOG4J2-1812 Project: Log4j 2

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

Remko Popma created LOG4J2-1811: --- Summary: Log4j 2 configuration/usage ergonomics Key: LOG4J2-1811 URL: https://issues.apache.org/jira/browse/LOG4J2-1811 Project: Log4j 2 Issue Type: Epic

Re: Logback performance improvements

mbers on the Logback >>>>>> user’s list so he can add them to his spreadsheet. >>>>>> >>>>>> From your numbers and the numbers I’ve been getting, it is clear to me >>>>>> that the SSDs in Apple’s MacBook’s are pretty awesome. From the hardware >>>

Re: Regarding Checkstyle, PMD, and formatting

hile maintaining effective finality instead. I just wish Java > had final be the default. > > On 10 February 2017 at 05:34, Remko Popma <remko.po...@gmail.com> wrote: > >> Generally agree except that we agreed that the final qualifier was >> optional. This may not be

[jira] [Commented] (LOG4J2-1678) (GC) Avoid allocating temporary objects in ThreadContextMapFilter

[ https://issues.apache.org/jira/browse/LOG4J2-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15861335#comment-15861335 ] Remko Popma commented on LOG4J2-1678: - Can you provide details on why you think there's a problem

Re: Regarding Checkstyle, PMD, and formatting

Generally agree except that we agreed that the final qualifier was optional. This may not be easy (or possible?) to verify automatically anyway. Otherwise all looks reasonable. Sent from my iPhone > On Feb 10, 2017, at 17:55, Mikael Ståldal wrote: > > Seems

Re: Logback performance improvements

backFilethrpt 10 >> 1192.594 ± 57.777 ops/ms >> >> I will try the other machines later and post those results. >> >> Ralph >> >> >> On Feb 9, 2017, at 5:22 AM, Apache <ralph.go...@dslextreme.com> wrote: >> >> Ceki r

Re: Logback performance improvements

ded, not the encoder, so it looks like the confit needs to be > changed and the test rerun. > > Ralph > > On Feb 9, 2017, at 3:08 AM, Remko Popma <remko.po...@gmail.com> wrote: > > FYI, The write and flush methods in BufferedOutputStream are also > synchronized, so w

Re: Logback performance improvements

FYI, The write and flush methods in BufferedOutputStream are also synchronized, so we won't be able to do away with synchronization completely. In OutputStreamManager we synchronize multiple methods but these are nested calls. I thought reentrant synchronization had negligible overhead but I

Re: Logback performance improvements

I will try taking a look when I get home from work tonight. Ceki reported some strange numbers about Log4j 1 outperforming Log4j2 before, and when we showed results from 3 or 4 environments that disproved his claims, he never really explained how that happened. Not sure if there's some issue

Re: Logback performance improvements

AM, Apache <ralph.go...@dslextreme.com> wrote: >> >> True, but I would still like to also see what difference it makes using the >> FileChannel instead of the OutputStream. >> >> Ralph >> >>> On Feb 7, 2017, at 9:45 AM, Remko Popma <remko.

Re: Logback performance improvements

gt; now that I can't even remember the last time I had to write an actual lock. >> >> On 6 February 2017 at 22:02, Apache <ralph.go...@dslextreme.com> wrote: >> >>> Logback 1.2-SNAPSHOT >>> >>> Ralph >>> >>> On Feb 6, 2017,

Re: Logback performance improvements

Sorry what 1.2 do you mean? Sent from my iPhone > On Feb 7, 2017, at 11:06, Apache wrote: > > In 1.2? That may work for a FileOutputStream but it isn’t guaranteed to work > for others. > > Ralph > >> On Feb 6, 2017, at 5:23 PM, Matt Sicker

Re: Java 9

t; On Feb 6, 2017, at 9:15 AM, Matt Sicker <boa...@gmail.com> wrote: >> >> I remember Ralph mentioned that he tested it out and found that it worked >> pretty well. See issue: <https://issues.apache.org/jira/browse/LOG4J2-1359> >> >> On 6 February 2017 at

Java 9

I haven't had a chance to look at this yet, but is the new stack walking API in Java 9 of any use for us? I believe applications/libraries like Log4j were supposed to be the drivers behind this feature, but last time I checked they were not going to cater for our use case (inspect the stack from

[jira] [Commented] (LOG4J2-1809) Add global configuration environment SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853416#comment-15853416 ] Remko Popma commented on LOG4J2-1809: - Where will this interface be used? Inside PropertiesUtil

[jira] [Commented] (LOG4J2-1808) java.lang.NoSuchMethodError: org.apache.logging.log4j.ThreadContext.getThreadContextMap()

[ https://issues.apache.org/jira/browse/LOG4J2-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853001#comment-15853001 ] Remko Popma commented on LOG4J2-1808: - The method {{ThreadContext.getThreadContextMap()}} was added

Re: SyslogAppender parameter name change

>), >> don't recall if attributes are supported. If not, that's a feature we can >> support for sure. >> >>> On 2 February 2017 at 18:27, Gary Gregory <garydgreg...@gmail.com> wrote: >>> Darn, I apologize for that one. >>> >>> Gary >

  1   2   3   4   5   6   7   8   9   10   >