Re: [log4j] The shape of Log4j

I’m still not convinced that moving the items that Ralph enumerated out of core will make a significant difference in the time it takes to do a release (I believe other measures will be more effective), but fine. If Ralph wants this as a precondition to continue to perform the Log4j2 releases

Re: logging-log4j2 git commit: LOG4J2-1883 moved SystemMillisClock out of the java9 module into core so it can be used with any supported Java version

> > > > > > > > > On Wed, Jan 24, 2018 at 8:58 AM, Remko Popma > > > wrote: > > > > > >> I see what you mean. Hmm... > > >> > > >> FYI, this feature (LOG4J2-1883) adds the following classes. I ad

Re: logging-log4j2 git commit: LOG4J2-1883 moved SystemMillisClock out of the java9 module into core so it can be used with any supported Java version

I moved the new precise time-related classes to a new package core.time as requested by Gary. Note that the preexisting time-related classes in util cannot be moved as that would break user code. On Fri, Jan 26, 2018 at 8:59 PM, Remko Popma wrote: > I renamed DummyPreciseClock

Re: remove Chainsaw's site code from git?

No objection from me. We may want to think about how to maintain the Chainsaw site going forward, but having a stale duplicate is asking for problems so I’d say remove it ASAP. (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 27, 2018, at 6:19, Scott Deboy wrote

Re: logging-log4j2 git commit: LOG4J2-1883 moved SystemMillisClock out of the java9 module into core so it can be used with any supported Java version

> On Jan 26, 2018, at 21:19, Remko Popma wrote: > > I moved the new precise time-related classes to a new package core.time as > requested by Gary. > > Note that the preexisting time-related classes in util cannot be moved as > that would break user code. I’m actually s

Re: logging-log4j2 git commit: LOG4J2-1883 moved SystemMillisClock out of the java9 module into core so it can be used with any supported Java version

On Sat, Jan 27, 2018 at 8:30 Remko Popma wrote: > > On Jan 26, 2018, at 21:19, Remko Popma wrote: > > I moved the new precise time-related classes to a new package core.time as > requested by Gary. > > Note that the preexisting time-related classes in util cannot be moved

Re: logging-log4j2 git commit: LOG4J2-1883 moved SystemMillisClock out of the java9 module into core so it can be used with any supported Java version

he related classes in the same package is more > important than them residing in the package with the best name. > > Ralph > > > > On Jan 26, 2018, at 5:09 PM, Remko Popma wrote: > > > > On Sat, Jan 27, 2018 at 8:30 Remko Popma wrote: > > > >> > &g

Re: [log4j] The shape of Log4j

Perhaps https://issues.apache.org/jira/browse/LOG4J2-2226 (Log4j2 modularization) can also function as the epic for moving towards the plugin API that Matt mentioned. (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 25, 2018, at 9:45, Matt Sicker wrote: > > I'm

Re: New time classes and Java 8

Well, we can’t use java.time.Instant in LogEvent and still be garbage free. So that’s a bigger discussion. You have reviewed the code, so I hope you agree, but I think our new time code is pretty clean. One could argue that the translation from epochSeconds to epochMillis is duplication from j

Re: Soliciting input: ElasticSearch receiver

Sorry I won’t be able to help you with that; no experience with ElasticSearch. Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 28, 2018, at 9:48, Scott Deboy wrote: > > I'm looking at adding an ES receiver and was curious what folks would > like to see w

Re: Regression from 2.9.1 to 2.10.0 - win7/jdk1.8.0_152 - always getting ERROR StatusLogger Log4j2 could not find a logging implementation.

Thanks for the clarification! Good to hear. On Sun, Jan 28, 2018 at 11:34 PM, wrote: > This was a local issue. Something was corrupt about the core jar and once > I replaced it with a known good file things worked as expected. > > Apologies if anybody wasted time looking into this non-issue. > >

Re: [log4j] org.apache.logging.log4j.core.appender.mom.jeromq move?

Our release notes are going to need a section “Potential breaking changes”. We should start tracking these before we forget. (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 29, 2018, at 6:25, Ralph Goers wrote: > > I should add that each module must have a uni

Re: [log4j] org.apache.logging.log4j.core.appender.mom.jeromq move?

Gary, Would you mind changing the epic link of these and future JIRA tickets to https://issues.apache.org/jira/browse/LOG4J2-2226 (Log4j core modularization)? That’s a nice way to link them together. (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 29, 2018, at

Re: logging-log4j2 git commit: In-line mutable local vars.

I actually coded it this way deliberately. The local variables clarify the intention and make the code self documenting. Without the variable the reader needs to spend effort to understand the calculation on the right. I got this technique from Kent Beck’s Implementation Patterns and Robert M

Re: [log4j] org.apache.logging.log4j.core.appender.mom.jeromq move?

I went ahead and changed the epic link on the JIRA tickets related to splitting off sub modules. Hope you don’t mind. On Mon, Jan 29, 2018 at 7:16 Remko Popma wrote: > Gary, > > Would you mind changing the epic link of these and future JIRA tickets to > https://issues.apache.org

Re: logging-log4j2 git commit: In-line mutable local vars.

On Mon, Jan 29, 2018 at 7:39 AM, Remko Popma wrote: > I actually coded it this way deliberately. > The local variables clarify the intention and make the code self > documenting. Without the variable the reader needs to spend effort to > understand the calculation on the right. &g

[log4j] clarify "internal" vs exported packages in core - plugin API

If we are going to make breaking changes in this release it may be wise to also do any package renaming in this release to keep the disruption limited to a single release instead of multiple. Specifically, I propose we take this release to do all package renaming to clarify the difference between

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

t a release before all > this modularization work and then created a branch so we could maintain it > if necessary. > > Ralph > > > On Jan 29, 2018, at 10:04 AM, Gary Gregory > wrote: > > > > On Mon, Jan 29, 2018 at 8:17 AM, Remko Popma > wrote: > >

Re: Java 8

I am neutral about moving to Java 8 soon. We have just recently started to make a lot of package rename changes that really belong in 3.0 and not in 2.11... We should consider doing a 2.11 release from a commit before we started to rename packages. Then doing the modules split-off and clarifying

Re: Java 8

If we want to do a 2.11 release that is binary compatible, I believe that commit 21bc3aa is the last commit to include. >From the following commit (ba658a0) we start to move classes and rename packages - this would better fit in a 3.0 release where users would expect some breaking changes in core.

Re: Java 8

The log4j-api module could benefit from a util.internal package where we move the util classes that are private and should not be exported. Potentially an idea for a 3.0 release. (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 30, 2018, at 2:41, Remko Po

Re: Java 8

I will fix picocli before we get to that point. (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 30, 2018, at 4:07, Gary Gregory wrote: > >> On Mon, Jan 29, 2018 at 11:07 AM, Remko Popma wrote: >> >> The log4j-api module could bene

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

therefore name the next release 3.0 to signal this incompatibility to users. Having a 3.0 release doesn’t necessarily mean we immediately start requiring Java 8. That can could come in a subsequent release. On Tue, Jan 30, 2018 at 2:26 Remko Popma wrote: > I agree with Ralph. > We can still d

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

> Ralph > >> On Jan 29, 2018, at 4:19 PM, Remko Popma wrote: >> >> Any feedback on the idea to cut a branch from commit 21bc3aa and release >> 2.11 from that branch? >> >> In the release notes we can announce that the next release will have >> inte

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

If you want I can create a “release-2.11” or “release-2.x” branch from that commit. > On Jan 30, 2018, at 14:17, Remko Popma wrote: > > I think it’s possible to search for a commit hash in IntelliJ, but here is a > github link: > https://github.com/apache/loggin

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

I created branch "release-2.x". On Tue, Jan 30, 2018 at 6:45 PM, Apache wrote: > That spot looks ok to me. Please make the branch > > Sent from my iPad > > > On Jan 29, 2018, at 10:43 PM, Remko Popma wrote: > > > > If you want I can create a “release-2

Re: [logging-log4j2] Git Push Summary

And we should update changes.xml in master. On Tue, Jan 30, 2018 at 10:56 PM, Gary Gregory wrote: > We need another Jenkins build for this. We should also change the POM > version in git master to avoid mixing things up. > > Gary > -- Forwarded message -- > From: > Date: Jan 30,

Re: [1/2] logging-log4j2 git commit: LOG4J2-2236 Removed unnecessary dependency on jcommander since Log4j uses embedded picocli since 2.9.

> On Jan 30, 2018, at 23:10, rpo...@apache.org wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master b5d4655d3 -> 136dbf5b5 > > > LOG4J2-2236 Removed unnecessary dependency on jcommander since Log4j uses > embedded picocli since 2.9. > > (cherry picked from commit 4da

Re: logging-log4j2 git commit: Update changes.xml: moved JIRA tickets that are not included in the 2.11 release to the 3.0 section

The JIRA tickets themselves are still marked as Fixed Version 2.11, Gary, would you mind updating them? On Thu, Feb 1, 2018 at 9:09 PM, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 041fe8ffe -> a9e8f525a > > > Update changes.xml: moved JIRA tickets that are not i

[log4j] which branches can be deleted?

Can some of these branches be deleted? >git branch -r --list origin/2.0-beta1 origin/AutoCloseableLock origin/GenericMapMessage origin/GenericMapMessageSimple origin/LOG4J2-1116 (Web app-friendly thread locals for gc-free logging (was: upgrade to log4j2 causes too frequent minor gc)) o

Re: Extend daily log file appender

Take a look at the RewriteAppender (https://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender). That may be a good start. Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Feb 2, 2018, at 21:48, Walter Heestermans (TME) > wrote: > > I take a

Re: Log4j Audit

Some first impression feedback: Top page: I think it is worth explaining the motivation/use case for audit logging here. What is "audit logging"? How is audit logging different from "normal" logging? What kind of applications would want to use audit logging and why? What are audit events? How do a

Re: Log4j Audit

og4j Audit API) all give 404 page not found errors. On Mon, Feb 5, 2018 at 11:49 PM, Remko Popma wrote: > Some first impression feedback: > > Top page: > I think it is worth explaining the motivation/use case for audit logging > here. What is "audit logging"? How is a

Re: [log4j] NUL in log event message

How about stripping nulls out of any error messages coming from Jansi? (Shameless plug) Every java main() method deserves http://picocli.info > On Feb 9, 2018, at 5:03, Gary Gregory wrote: > > It might be a bug in JAnsi's WindowsSupport.getLastErrorMessage() > > Gary > > On Thu, Feb 8, 2018 a

Re: [log4j] NUL in log event message

simplest thing > to do and leaves room for someone to investigate why JAnsi returns such a > string since at least you can see it. > > Gary > >> On Thu, Feb 8, 2018 at 5:40 PM, Matt Sicker wrote: >> >> Could that be UTF-16 or something similar? >> >>&g

Re: Log4j Audit

’d appreciate you and everyone else taking another > look at https://rgoers.github.io/log4j-audit/index.html > <https://rgoers.github.io/log4j-audit/index.html>. > > Thanks, > Ralph > >> On Feb 5, 2018, at 8:04 AM, Remko Popma wrote: >> >> Ab

Re: Log4j Audit

dit logging with the generated interfaces, without RequestContext (perhaps for a non-web app). I'll stop here. Let me know what you think. Remko On Mon, Feb 12, 2018 at 11:01 Remko Popma wrote: > Ok, I’ll try tonight if I can. > > > > > On Feb 12, 2018, at 9:31, Ralph Goer

Re: Java 8

gh. > > Ralph > > > >> On Feb 12, 2018, at 2:08 PM, Gary Gregory wrote: >> >> Hi All: >> >> Any thoughts on the timing for 2.11.0? >> >> Gary >> >>> On Mon, Jan 29, 2018 at 3:00 PM, Remko Popma wrote: >>

Re: [1/2] logging-log4j2 git commit: LOG4J2-2250 The internal status logger timestamp format is now configurable with system property `log4j2.StatusLogger.dateformat`.

Matt, sure, this can be changed. I won't be able to do it tonight though. On Fri, Feb 16, 2018 at 11:03 PM, Matt Sicker wrote: > Is this property name already set in stone? Why not log4j2. > StatusLogger.DateFormat? > > On 15 February 2018 at 21:59, wrote: > > > Repository: logging-log4j2 > > U

Re: Jenkins build became unstable: Log4j 2 3.x #18

This is likely my last commit. I’ll look into this tomorrow. > On Feb 26, 2018, at 21:06, Apache Jenkins Server > wrote: > > See > >

Re: Jenkins build became unstable: Log4j 2 3.x #18

Strange, master builds fine on my machine. CloseableThreadContextTest also all pass on my machine. On Mon, Feb 26, 2018 at 10:22 PM, Remko Popma wrote: > This is likely my last commit. > I’ll look into this tomorrow. > > > > On Feb 26, 2018, at 21:06, Apache Jenki

Re: JDK 10: Release Candidate & JDK 11 Early Access builds available

I didn't see anything in http://jdk.java.net/10/release-notes that seemed relevant for Log4j... On Sat, Mar 3, 2018 at 12:05 AM, Ralph Goers wrote: > If somebody sees something in Java 10 or 11 that we should support please > speak up. So far, I don’t. > > Ralph > > > On Mar 2, 2018, at 4:03 AM,

Re: org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does not use Charset

(Away from pc) by “use”, do you mean that the string returned by getContentType() doesn’t include a charset? From memory, I remember the only place this method is used is in the HtmlAppender. Are there other places? (Shameless plug) Every java main() method deserves http://picocli.info > On Ma

Re: org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does not use Charset

return The default content type for Strings. >>> */ >>>@Override >>>public String getContentType() { >>>return "text/plain"; >>>} >>> >>> Gary >>> >>> >>> >>> On

Re: Building log4j2 from console supporting ANSI colors fails

Thanks for reporting this. I’ll take a look. Remko > On Mar 11, 2018, at 17:32, Atle Tokle wrote: > > I tried to build from GIT bash on windows 10, and first test that failed > was > > testSynopsisOrderCorrectWhenParametersDeclaredOutOfOrder in > > org.apache.logging.log4j.core.tools.picocl

Re: 2.11.0 status

Matt is right on all counts. The tests can be removed since picocli is tested in its own project, and when we split the modules it can be moved out of core into the tools module. > On Mar 12, 2018, at 8:03, Matt Sicker wrote: > > Is that test copied from picocli? If so, I’m not sure what th

Traveling

FYI I am traveling with family. I’ll have sporadic access to web and email. I’ll try to review the release though. Remko

Re: [VOTE] Release Log4j 2.11.0-rc1

+1 checksums good, site looks good (other than the issues already pointed out by others) On Mon, Mar 12, 2018 at 8:50 AM, Ralph Goers wrote: > This is a vote to release Log4j 2.11.0, the next version of the Log4j 2 > project. > > Please download, test, and cast your votes on the log4j developer

Re: [log4j] providing sourcewith Message

I am interested and planning to take a look if others don’t beat me to it. Is there a corresponding JIRA ticket? (Shameless plug) Every java main() method deserves http://picocli.info > On Mar 16, 2018, at 5:33, Jeffrey Shaw wrote: > > Hi, just hoping to get some eyes on this again. > >> On F

Re: [ANNOUNCEMENT] (Corrected) Apache Log4j 2.11.0 released

Blogged: Log4j 2.11 released : Apache Logging Services | | | | Log4j 2.11 released : Apache Logging Services | | | Please share on social media! On Saturday, March 17, 2018, 9:49:22 AM GMT+9, Ralph Goers wrote: The Apache Log4j 2 team is pleased to announce the Log4j 2.11

Re: [ANNOUNCEMENT] (Corrected) Apache Log4j 2.11.0 released

Blogged: https://blogs.apache.org/logging/entry/log4j-2-11-released Please share on social media! On Sat, Mar 17, 2018 at 9:49 AM, Ralph Goers wrote: > The Apache Log4j 2 team is pleased to announce the Log4j 2.11.0 release! > > Apache Log4j is a well known framework for logging application b

Re: Support for 2.x

Makes perfect sense to me. > On Mar 19, 2018, at 2:10, Ralph Goers wrote: > > Although I would like to see us start doing 3.x releases I don’t think it is > time to stop supporting 2.x. To that end, where applicable I think we should > continue applying patches to both the release-2.x branc

Re: Log4j Audit

Started looking. It’s much more accessible than the initial version. Nice! I need some more time to give detailed feedback. (Shameless plug) Every java main() method deserves http://picocli.info > On Mar 19, 2018, at 14:03, Ralph Goers wrote: > > I have updated both the catalog editor and the

Re: Building log4j2 from console supporting ANSI colors fails

p.Ansi.OFF as it's third argument. I can send you patch if > you tell me how you want it. > > Atle > > > Den søn. 11. mar. 2018 kl. 11:04 skrev Remko Popma >: > > > Thanks for reporting this. I’ll take a look. > > > > Remko > > > > > On Ma

Re: 2.11.0 status

These tests have been removed. On Mon, Mar 12, 2018 at 10:58 AM, Remko Popma wrote: > Matt is right on all counts. The tests can be removed since picocli is > tested in its own project, and when we split the modules it can be moved > out of core into the tools module. > > > &

Re: Building log4j2 from console supporting ANSI colors fails

These tests have been removed. On Wed, Mar 21, 2018 at 7:39 PM, Remko Popma wrote: > We will probably just remove these tests; there is no need to bring the > picocli tests in to the Log4j2 project. > > On Wed, Mar 21, 2018 at 3:20 PM, Atle Tokle wrote: > >> I made a fr

Re: Building log4j2 from console supporting ANSI colors fails

t's third argument. I can send you patch if >>> you tell me how you want it. >>> >>> Atle >>> >>> >>>> Den søn. 11. mar. 2018 kl. 11:04 skrev Remko Popma : >>>> &g

Re: [VOTE][LAZY] Release Logging Parent version 2

+1 (Shameless plug) Every java main() method deserves http://picocli.info Remko > On Mar 25, 2018, at 3:44, Matt Sicker wrote: > > Apologies for the typo. the gpg command to update my key is actually: > > gpg --recv-keys 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D > >> On 24 March 2018 at 13:4

Re: [Scala] New site preview

Nice work! I love AsciiDoc, it looks great and is super easy to maintain! The only drawback of AsciiDoc is that I haven’t found a way yet to have a navigation menu at the top to link multiple pages together. (Not strictly a drawback of AsciiDoc itself.) One small issue: the 4th row in the tabl

Re: [Scala] New site preview

trouble imagining what this means. (Shameless plug) Every java main() method deserves http://picocli.info > On Apr 1, 2018, at 12:12, Remko Popma wrote: > > Nice work! > I love AsciiDoc, it looks great and is super easy to maintain! > > The only drawback of AsciiDoc is that I h

Re: [Scala] New site preview

at 13:50, Remko Popma wrote: > > One more: the section under Logger Names says “The Logging trait will > automatically name the Logger accordingly to the class it is being used in”, > and suggests this is somehow different than the dot-separated hierarchy in > Java. An examp

Re: [Scala] New site preview

One more: typo “Support for Scala versions 2.10, 2.11, and 2.12 are provided,” should be “... is provided” (Shameless plug) Every java main() method deserves http://picocli.info > On Apr 1, 2018, at 13:56, Remko Popma wrote: > > Ah, got it now. How about this? > > “... The

Re: Console performance

Yes writing to the console on either Windows or Linux was ~50x(!) slower than writing to a file. This is documented on the log4j performance page. Mikael’s JIRA ticket on the direct option has some perf numbers: https://issues.apache.org/jira/browse/LOG4J2-1395 I seem to remember that the direc

Re: [Log4j] Using AsciiDoc in more places

I'm definitely +1 on AsciiDoc to replace Markdown. I am not sure if there is a nice way to make a full coherent site out of AsciiDoc pages; I haven't found a good way to link these pages with something like a shared top navigation menu or so. I end up creating a section (which shows up in the left

Re: [Log4j] Windows build failures on Jenkins

Carter, To me it’s sufficient due diligence when you’ve run the tests on your machine. The continuous integration builds are a smoke test to flush out issues on other environments. They sometimes show issues none of us see when building locally. I would only consider a failing test to break t

Re: [log4j] Thoughts on adding log4j2.forceTCLOnly option (#140)

I’m not enough of an expert on class loaders to make a judgement call one way or the other. (Shameless plug) Every java main() method deserves http://picocli.info > On Apr 9, 2018, at 2:32, Gary Gregory wrote: > > Any thoughts on this PR? > > Gary > > -- Forwarded message --

Re: [log4j] com.lmax.disruptor.collections.Histogram gone in LMAX 3.4.x

We should probably migrate to HdrHistogram, but I don’t have time to do that work now. (Shameless plug) Every java main() method deserves http://picocli.info > On Apr 9, 2018, at 7:12, Gary Gregory wrote: > > Hi All: > > It looks like LMAX removed com.lmax.disruptor.collections.Histogram in

Re: [log4j]

I saw some commits flying by in that area recently but I didn’t look closely. Could that be related? Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Apr 11, 2018, at 4:50, Gary Gregory wrote: > > When I change my log4j XML config file and I have status loggi

Re: [log4j] Curious about WatchManager implementation

I remember Ralph looked at it but concluded it wasn’t fit for purpose. I forget the details but it’s on the mailing list somewhere. Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Apr 13, 2018, at 0:10, Gary Gregory wrote: > > Hi All: > > Our WatchManager p

Traveling

FYI I’m traveling in Europe with family and I’ll have sporadic access to internet. Remko

Re: [VOTE] Migrate git repositories to gitbox

+1 On Sat, Apr 28, 2018 at 11:48 PM, Gary Gregory wrote: > +1 > > Gary > > On Sat, Apr 28, 2018, 17:12 Matt Sicker wrote: > > > This is a vote to migrate from the existing git-wip-us infrastructure to > > the currently supported gitbox infrastructure that Infra advocates for > > using nowadays.

Re: Proposal on how to handle java doc @since tags and related

Good idea. At work we use version NEXT in a similar way. Works quite well. Remko (Shameless plug) Every java main() method deserves http://picocli.info > On May 2, 2018, at 17:57, Matt Sicker wrote: > > This is more important for public APIs, but adding @since version tags are > helpful for

Re: Log4j-audit release

I’ll be flying back to Tokyo tomorrow but I can take another look when I’m back. Is there a recent snapshot of the site on your GitHub account? > On May 6, 2018, at 21:35, Ralph Goers wrote: > > I have finished everything I wanted to accomplish for the first release of > log4j-audit and so I

Re: Async Appenders

Log4j core provides about 4 flavours of async logging, several of which use non-blocking data structures. Can you link to the ones you think should be included? Thanks! Remko (Shameless plug) Every java main() method deserves http://picocli.info > On May 7, 2018, at 14:15, William Davis wr

Re: Log4j-audit release

; On 6 May 2018 at 16:26, Ralph Goers wrote: > > > I spoke too soon. I made a minor change to add a link to Apache events in > > the site header. > > > > Ralph > > > > > On May 6, 2018, at 2:24 PM, Ralph Goers > > wrote: > > > > > >

Re: [jira] [Closed] (LOG4J2-2337) JSONLayout printing \r at end of line

Gary, why did you close that ticket? This is a valid technical question about log4j 2, and I see absolutely nothing wrong with using the log4j 2 JIRA for it. The JIRA notifications are captured on the mailing list, fulfilling the Apache requirements. Our web site gives no indication whatsoeve

Re: [jira] [Closed] (LOG4J2-2337) JSONLayout printing \r at end of line

> to Jira either out of ignorance, or for not wanting to subscribe to a > mailing list before posting. > > I see Jira first as a bug tracking system and second as a project > management tool. Using Jira to answer user queries will just clog up the > system. > > Gary >

Re: [jira] [Closed] (LOG4J2-2337) JSONLayout printing \r at end of line

> On May 9, 2018, at 13:55, Gary Gregory wrote: > > It's a distinction we make over at Commons IIRC. I hope for the sake of the users that the Commons website documents this requirement then. :-) > > Gary > >> On Tue, May 8, 2018 at 10:04 PM, Remko Popma wrote

Re: [jira] [Closed] (LOG4J2-2337) JSONLayout printing \r at end of line

, Gary Gregory wrote: >> >> It's a distinction we make over at Commons IIRC. >> >> Gary >> >>> On Tue, May 8, 2018 at 10:04 PM, Remko Popma wrote: >>> >>> >>> We have not made clear to users (on our website or anywhere) tha

Re: Async Appenders

In the log4j world, async logging means adding the information to be logged to some data structure, whereupon the application thread returns immediately to do other work. In the background, another thread reads the information to be logged from the data structure, potentially transforms it, the

Re: Async Appenders

s >>>> best >>>>> with io, it also works with cpu intensive tasks that need to be run on >>>>> background threads. But using this for computational expensive cpu >> tasks >>>>> only pays off it the costs of synchronization and context switches

Re: Log4j-audit release

> > vote -1 on a release candidate? While I think the documentation should > be > > good I don’t think it has to be perfect. > > > > Although I have been using it in production for a while it would be great > > if someone else could give it a try. > > > &

Re: Log4j-audit release

comments in the documentation. I > have updated my web site accordingly. Some comments are below. > > I really would like feedback on more than just the site as I need to > release this. > > > On May 7, 2018, at 5:42 PM, Remko Popma wrote: > > > > I had time to

Re: Log4j-audit release

pps\jdk1.8.0_161\jre Default locale: en_GB, platform encoding: MS932 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" On Sun, Jun 10, 2018 at 4:21 PM, Remko Popma wrote: > getting this now > > [INFO] Re

Re: Log4j-audit release

e catalog’s usefulness really comes into > > play > > >>>> when you want to create a UI to query and display the audit events. > In > > >> that > > >>>> case associating events with products and/or categories can be quite > > >>>

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

+1 (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 13, 2018, at 9:03, Gary Gregory wrote: > > I started reading the site, which is good so far... should be able to > continue tomorrow... > > Gary > >> On Tue, Jun 12, 2018, 17:35 Ralph Goers wrote: >> >> 48 ho

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

About the logo: I would prefer that everywhere we use it we stick to the Log4j 2 logo as it was designed and not change the colors or pattern any more. The original looks much more clean and professional. > On Jun 18, 2018, at 2:06, Ralph Goers wrote: > > Thanks Matt! > > Any help you want

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

It’s the one called logo.jpg. All png logo files are our modified versions AFAICS. > On Jun 18, 2018, at 13:08, Ralph Goers wrote: > > I’m OK with that, assuming I can remember which one it was. > > Ralph > >> On Jun 17, 2018, at 3:53 PM, Remko Popma wrote: >&g

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

I should be able to blog this announcement tomorrow morning but now it’s bedtime for me. :-) (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 23, 2018, at 0:39, Ralph Goers wrote: > > The Apache Log4j team is pleased to announce the Apache Log4j Audit 1.0.0 > r

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

: You could always wait until Monday to post it to get more views. :) On 22 June 2018 at 11:28, Remko Popma wrote: I should be able to blog this announcement tomorrow morning but now it’s bedtime for me. :-) (Shameless plug) Every java main() method deserves http://picocli.info > On Jun

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

(Re-posting since I did not see the link when sending from my yahoo mail account.) Blogged: https://blogs.apache.org/logging/entry/announce-apache-log4j-audit-1 Please share on social media! Thanks, -Remko On Mon, Jun 25, 2018 at 7:48 PM, Remko Popma wrote: > Blogged: [ANNOUNCE] Apache Lo

Re: [Log4j2] RollingFileAppender ignores immediateFlush

Be careful in this area. I remember this was quite tricky! Please step through the code in a debugger to make sure it does what you think it does before making changes. Remko > On Jul 14, 2018, at 9: 27, Gary Gregory wrote: > >> On Fri, Jul 13, 2018 at 6:22 PM Gary Gregory wrote: >> >> H

Re: [Log4j2] RollingFileAppender ignores immediateFlush

> On Jul 14, 2018, at 10:49, Remko Popma wrote: > > Be careful in this area. I remember this was quite tricky! > > Please step through the code in a debugger to make sure it does what you > think it does before making changes. Also maybe start with a failing test case.

Re: [VOTE] Release Log4j 2.11.1-rc1

+1 On Wed, Jul 25, 2018 at 5:00 AM, Matt Sicker wrote: > +1 > > Builds with Java 8 and 10 toolchain, though I had to add a dummy entry in > my toolchains.xml for 9 for one of the modules (it should request a version > range). Signatures good. Site looks fine, though I haven't looked through > it

Carter Kozak joined the Apache Logging PMC

We are very happy that Carter Kozak joined the Apache Logging Services PMC. He has made many contributions to the development of Log4j 2 especially in the areas of concurrency, performance and memory management. Thanks Carter for all you did so far and all the best for your new role at Apache Loggi

Fwd: [ANNOUNCE] Apache Log4j 2.11.1 released

Blogged: https://blogs.apache.org/logging/entry/log4j-2-11-1-released Please share on social media. On Tue, Jul 31, 2018 at 2:38 PM, Ralph Goers wrote: > > The Apache Log4j 2 team is pleased to announce the Log4j 2.11.1 release! > > Apache Log4j is a well known framework for logging application

Re: Logging and containers

It may be to do with whether a tty is attached and how fast it is: https://stackoverflow.com/questions/3857052/why-is-printing-to-stdout-so-slow-can-it-be-sped-up (Shameless plug) Every java main() method deserves http://picocli.info > On Aug 6, 2018, at 4:21, Ralph Goers wrote: > > Our perfor

Re: Logging and containers

e.com > > > > > >>> wrote: > > >>> > > >>>> So that begs the question, when logging to stdout in a container is > a > > >>>> console attached? i.e. can you normally view the output like you > > could in a > >

Re: [GitHub] logging-log4j2 pull request #202: [LOG4J2-2391] Improve ThrowableProxy perfo...

What I remember from email interactions that Ralph had with the people working on the Stackwalker implementation: Ostensibly Stackwalker was supposed to give performance benefits for use cases like ours. They even mentioned discovering the location of a logging call as one of the main use cases

[log4cxx] logging web page broken link

>From the logging page (http://logging.apache.org/) if you click on the log4cxx project page button, it sends you to https://logging.apache.org/log4cxx/latest_stable/latest_stable/ with a Page Not Found error page...

<    1   2   3   4   5   6   >