Fwd: [apache/logging-log4j2] Documentation bug for purgeAscending method. (#41)

Who knows this code best to see if this patch makes sense? Gary -- Forwarded message -- From: challarao Date: Fri, Aug 26, 2016 at 3:48 PM Subject: [apache/logging-log4j2] Documentation bug for purgeAscending method. (#41) To: apache/logging-log4j2

[jira] [Comment Edited] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495203#comment-15495203 ] Di Shang edited comment on LOG4J2-1585 at 9/16/16 2:57 AM: --- I'm implementing a

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495205#comment-15495205 ] Matt Sicker commented on LOG4J2-1585: - I think you'd need to add Marker support to SimpleLogger in

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495203#comment-15495203 ] Di Shang commented on LOG4J2-1585: -- I'm implementing a dynamic cascading filtering system where I can

[jira] [Commented] (LOG4J2-1586) Automatic Reconfiguration not working when edit and save log4j2.xml in NetBeans /build/WEB-INF

[ https://issues.apache.org/jira/browse/LOG4J2-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495016#comment-15495016 ] Darren Kelly commented on LOG4J2-1586: -- [~rkpkuipers] There is no problem when I use: {code}

[jira] [Updated] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry West updated LOG4J2-1583: --- Affects Version/s: (was: 2.5) 2.6.1 > Nested logging call disrupts output

[jira] [Commented] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494962#comment-15494962 ] Larry West commented on LOG4J2-1583: [~mikaza] hmm... you're right. I misread my own sample output:

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494858#comment-15494858 ] Gary Gregory commented on LOG4J2-1585: -- Dare we introduce support for Markers to the StatusLogger in

Jenkins build became unstable: Log4j 2.x #2322

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

Re: Async tests with ListAppender

Since it wasn’t designed to be used in a multi-threaded test it would be a mistake to do that. I don’t know that I have written any multi-threaded tests that use it. Ralph > On Sep 15, 2016, at 12:25 PM, Gary Gregory wrote: > > Well, that was my initial question.

Re: Async tests with ListAppender

Well, that was my initial question. Since we use ListAppender all over our tests, ARE WE in fact using it from IN ANY multithreaded manner? I do not know. If we are, then we might be getting lucky. I do not know. Gary On Thu, Sep 15, 2016 at 12:17 PM, Ralph Goers

Re: Async tests with ListAppender

Why are we even talking about this. Does someone really have a use case where they want to use the ListAppender in a multithreaded manner in a unit test? Ralph > On Sep 15, 2016, at 12:13 PM, Gary Gregory wrote: > > I'm not sure why. Probably because we want our test

Re: Async tests with ListAppender

I'm not sure why. Probably because we want our test code to be more like production code since tests show _how_ to use Log4j for some people. So we might as well do it in a way that is best. It seems that Java has a lot of concurrent classes that are designed to work better that a brute-force

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

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

Fwd: Jenkins build became unstable: Log4j 2.x #2320

This one is a test timeout out after 30 seconds on a build that normally passes. That machine must be slow or busy or both. I increased the TO to 60 seconds. Gary -- Forwarded message -- From: Apache Jenkins Server Date: Thu, Sep 15, 2016 at 11:19 AM

Re: Roadmap for 3.0

Ah, yes, Java 9... it just seems that we need to more clearly define what is public vs. not and an SPI package seems like nice neat way to do that. That said, it's a lot of busy work and I am not 100% it is worth it. I am waffling. Gary On Thu, Sep 15, 2016 at 11:05 AM, Ralph Goers

Jenkins build became unstable: Log4j 2.x #2320

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

Re: Roadmap for 3.0

Yeah, agreed on the Java 9 bit. If it's impossible to make 2.x compatible with Java 9 without making backwards incompatible changes, that might be the push needed to start planning for 3.0. On 15 September 2016 at 13:05, Ralph Goers wrote: > I am nowhere near wanting

Re: Roadmap for 3.0

I am nowhere near wanting to do 3.0. But we may want to do it for Java 9 depending on how disruptive that is. That is one of the reasons I would like to get moving on Java 9 asap. I have a feeling we may want to continue the 2.x releases while 3.x is going just for that reason. Ralph > On

[jira] [Commented] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493896#comment-15493896 ] Gary Gregory commented on LOG4J2-1587: -- There are Clirr alternatives of course. Apache Commons

Roadmap for 3.0

Hi All, Should we start thinking about 3.0 where the main driver is to formalize a Core SPI package? Doing this for 2.8 and break BC in Core would be too disruptive. Doing this for 2.8 and have a Core class implement a SPI interface where the SPI interface inherits the old interface would be

[jira] [Closed] (LOG4J2-1573) Layout is no longer optional

[ https://issues.apache.org/jira/browse/LOG4J2-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1573. Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.7 Closing per

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493867#comment-15493867 ] Gary Gregory commented on LOG4J2-1010: -- I wonder if we start to talk about a 3.0 roadmap which would

[jira] [Comment Edited] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493768#comment-15493768 ] Mikael Ståldal edited comment on LOG4J2-1465 at 9/15/16 4:08 PM: - I don't

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493768#comment-15493768 ] Mikael Ståldal commented on LOG4J2-1465: I don't think the current defaults for JmsAppender,

Re: Document where to find snapshot builds

Yes, but where? On Thu, Sep 15, 2016 at 5:50 PM, Remko Popma wrote: > If you want to document this, go for it! > > Sent from my iPhone > > On 2016/09/16, at 0:35, Gary Gregory wrote: > > +1 > > Gary > > On Thu, Sep 15, 2016 at 3:11 AM, Mikael

[jira] [Commented] (LOG4J2-1586) Automatic Reconfiguration not working when edit and save log4j2.xml in NetBeans /build/WEB-INF

[ https://issues.apache.org/jira/browse/LOG4J2-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493741#comment-15493741 ] Remko Popma commented on LOG4J2-1586: - Does the problem also occur if you specify the configuration

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493731#comment-15493731 ] Gary Gregory commented on LOG4J2-1465: -- This is what we have today: * ConsoleAppender -

Re: Document where to find snapshot builds

If you want to document this, go for it! Sent from my iPhone > On 2016/09/16, at 0:35, Gary Gregory wrote: > > +1 > > Gary > >> On Thu, Sep 15, 2016 at 3:11 AM, Mikael Ståldal >> wrote: >> We should document somewhere how to find snapshot

[jira] [Commented] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493723#comment-15493723 ] Remko Popma commented on LOG4J2-1583: - Thank you for the report! I will look into it this weekend.

Re: Document where to find snapshot builds

+1 Gary On Thu, Sep 15, 2016 at 3:11 AM, Mikael Ståldal wrote: > We should document somewhere how to find snapshot builds. Not every user > wants to build the project themselves. > > We need some instructions and this link: https://repository. >

Re: Misplaced class?

OK. On Thu, Sep 15, 2016 at 5:23 PM, Remko Popma wrote: > It is deliberately this way by design. The ThreadContextAccess class is > used by the context injector methods in the core module. > > This is private API and documented as such. However it needs to be in that >

Re: [1/2] logging-log4j2 git commit: Remove obsolete comment

Different strokes for different folks I guess. Do make sure you do update the Javadoc then, since you nuke it ;-) Gary On Thu, Sep 15, 2016 at 2:35 AM, Mikael Ståldal wrote: > I just got fed up with updating the Javadoc all the time during > development. We can add

Re: Misplaced class?

It is deliberately this way by design. The ThreadContextAccess class is used by the context injector methods in the core module. This is private API and documented as such. However it needs to be in that package in order to use the package protected method. The reason the ThreadContextAccess

[jira] [Commented] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493400#comment-15493400 ] Ralph Goers commented on LOG4J2-1587: - I have no plans to migrate the build process to Java 8 until

Re: Misplaced class?

OK, but should it then be in log4j-core module? Or log4j-api? On Thu, Sep 15, 2016 at 2:57 PM, Remko Popma wrote: > It is in that package so it can call package protected methods. > > Sent from my iPhone > > On 2016/09/15, at 21:41, Mikael Ståldal

[jira] [Commented] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493286#comment-15493286 ] Mikael Ståldal commented on LOG4J2-1583: Are you sure that this problem existed in 2.5? In that

[jira] [Updated] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1587: --- Description: The whole Maven build process, including {{site}}, should work on Java 8 (as

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493270#comment-15493270 ] Mikael Ståldal commented on LOG4J2-1576: OK, see

[jira] [Created] (LOG4J2-1587) Build process should work on Java 8

Mikael Ståldal created LOG4J2-1587: -- Summary: Build process should work on Java 8 Key: LOG4J2-1587 URL: https://issues.apache.org/jira/browse/LOG4J2-1587 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493257#comment-15493257 ] Mikael Ståldal commented on LOG4J2-1576: The upcoming Scala 2.12 will require Java 8. And if we

[jira] [Comment Edited] (LOG4J2-1573) Layout is no longer optional

[ https://issues.apache.org/jira/browse/LOG4J2-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493226#comment-15493226 ] Steffen Offermann edited comment on LOG4J2-1573 at 9/15/16 12:57 PM: -

[jira] [Commented] (LOG4J2-1573) Layout is no longer optional

[ https://issues.apache.org/jira/browse/LOG4J2-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493226#comment-15493226 ] Steffen Offermann commented on LOG4J2-1573: --- I don't have the time for a full application test

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493205#comment-15493205 ] Ralph Goers commented on LOG4J2-1576: - If the scala support is going to have different JDK

[jira] [Commented] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493200#comment-15493200 ] Ralph Goers commented on LOG4J2-1578: - I don't see how it would be. > RoutingAppender can be

Misplaced class?

Should the class ThreadContextAccess in log4j-core really be in package org.apache.logging.log4j? Shouldn't it be in org.apache.logging.log4j.core (or one of its subpackages)? -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com Grev Turegatan

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493187#comment-15493187 ] Mikael Ståldal commented on LOG4J2-1010: I suggest that {{ContextDataInjector}} is moved to the

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493156#comment-15493156 ] Remko Popma commented on LOG4J2-1576: - I see. Sorry for the confusion. My goal was not to make the

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493145#comment-15493145 ] Remko Popma commented on LOG4J2-1010: - What do you suggest and why? > Injectable context properties

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493121#comment-15493121 ] Mikael Ståldal commented on LOG4J2-1576: Yes, but you mentioned Java 8. > Better automated

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493113#comment-15493113 ] Remko Popma commented on LOG4J2-1576: - That's really a different issue though. This ticket is about

[jira] [Commented] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493107#comment-15493107 ] Mikael Ståldal commented on LOG4J2-1578: Could this be related to LOG4J2-1043 ? >

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493010#comment-15493010 ] Mikael Ståldal commented on LOG4J2-1576: Yes, we really need to get the whole build process to

[jira] [Commented] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492998#comment-15492998 ] Mikael Ståldal commented on LOG4J2-1572: The NDC pattern works slightly different than in Log4j

[jira] [Commented] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492986#comment-15492986 ] Johno Crawford commented on LOG4J2-1572: Verified null is no longer logged with 2.6.3-SNAPSHOT.

[jira] [Closed] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johno Crawford closed LOG4J2-1572. -- > Empty NDC stack logs null > - > > Key: LOG4J2-1572 >

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492969#comment-15492969 ] Mikael Ståldal commented on LOG4J2-1010: Should the {{ContextDataInjector}} interface really be

Re: @Required on layout on AbstractAppender

I would say no. It may make sense for some appenders to have a default layout, and we should keep it for those which already have it for BC reasons. But I don't think we should provide default layout for those appenders which do not already have it, and we should not force all future appenders to

[jira] [Created] (LOG4J2-1586) Automatic Reconfiguration not working when edit and save log4j2.xml in NetBeans /build/WEB-INF

Darren Kelly created LOG4J2-1586: Summary: Automatic Reconfiguration not working when edit and save log4j2.xml in NetBeans /build/WEB-INF Key: LOG4J2-1586 URL: https://issues.apache.org/jira/browse/LOG4J2-1586

Document where to find snapshot builds

We should document somewhere how to find snapshot builds. Not every user wants to build the project themselves. We need some instructions and this link: https://repository.apache.org/content/repositories/snapshots/ Should it be here: http://logging.apache.org/log4j/2.x/maven-artifacts.html ?

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492920#comment-15492920 ] Remko Popma commented on LOG4J2-1585: - The warning can be useful for some people so I don't think we

[jira] [Commented] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492917#comment-15492917 ] Mikael Ståldal commented on LOG4J2-1572: Yes, add our SNAPSHOT repository to your Maven settings,

[jira] [Commented] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492907#comment-15492907 ] Johno Crawford commented on LOG4J2-1572: [~mikaelstaldal] is there a Maven snapshot available? >

[jira] [Commented] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492884#comment-15492884 ] Mikael Ståldal commented on LOG4J2-1572: The fix for LOG4J-1530, which is already in master,

[jira] [Resolved] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1572. Resolution: Duplicate Fix Version/s: 2.7 > Empty NDC stack logs null >

[jira] [Assigned] (LOG4J2-1572) Empty NDC stack logs null

[ https://issues.apache.org/jira/browse/LOG4J2-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1572: -- Assignee: Mikael Ståldal > Empty NDC stack logs null > - > >

Re: Async tests with ListAppender

Why not a synchronized list? The performance might not be optimal, but probably be OK for unit tests. On Thu, Sep 8, 2016 at 10:34 PM, Gary Gregory wrote: > Should ListAppender use CopyOnWriteArray instead of ArrayList? Either all > the time or when using in aync tests?

Re: [1/2] logging-log4j2 git commit: Remove obsolete comment

I just got fed up with updating the Javadoc all the time during development. We can add the Javadoc back when we are done and this is about to be released, and also create some documentation. During development, JIRA is nice. On Thu, Sep 8, 2016 at 6:11 PM, Gary Gregory

[jira] [Closed] (LOG4J2-1051) NoClassDefFoundError when starting app on Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Lenart closed LOG4J2-1051. - > NoClassDefFoundError when starting app on Google App Engine >

[jira] [Commented] (LOG4J2-1051) NoClassDefFoundError when starting app on Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492772#comment-15492772 ] Lukasz Lenart commented on LOG4J2-1051: --- Confirmed, no more problems spotted, thanks! >

[jira] [Closed] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1528. -- > Serialize configuration into a log4j2.xml file > --

[jira] [Commented] (LOG4J2-1573) Layout is no longer optional

[ https://issues.apache.org/jira/browse/LOG4J2-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492589#comment-15492589 ] Gary Gregory commented on LOG4J2-1573: -- Thank you for the update. See you here later then. > Layout

[jira] [Updated] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1585: - Description: Hi I just noticed a lot of warning spam in my log like this: 2016-09-15

[jira] [Commented] (LOG4J2-1419) Memory leak on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492582#comment-15492582 ] Gary Gregory commented on LOG4J2-1419: -- Can you test your use case with the latest from Git master?

[jira] [Commented] (LOG4J2-1573) Layout is no longer optional

[ https://issues.apache.org/jira/browse/LOG4J2-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492583#comment-15492583 ] Steffen Offermann commented on LOG4J2-1573: --- I just did the test again with the latest

[jira] [Updated] (LOG4J2-1419) Memory leak on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1419: - Summary: Memory leak on Tomcat shutdown (was: Memory leak on tomcat shutdown) > Memory leak on

[jira] [Commented] (LOG4J2-1573) Layout is no longer optional

[ https://issues.apache.org/jira/browse/LOG4J2-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492579#comment-15492579 ] Gary Gregory commented on LOG4J2-1573: -- Hello [~SteffenO], Can you please clarify how your tests

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

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1259: - Summary: Log4j threads are leaking on Tomcat shutdown (was: Log4j threads are leaking on tomcat

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

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1259. Resolution: Fixed > Log4j threads are leaking on Tomcat shutdown >

[jira] [Reopened] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1259: -- > Log4j threads are leaking on tomcat shutdown > > >

[jira] [Created] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

Di Shang created LOG4J2-1585: Summary: Logger.getParent gives warning about MessageFactory mismatch Key: LOG4J2-1585 URL: https://issues.apache.org/jira/browse/LOG4J2-1585 Project: Log4j 2

[jira] [Closed] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1259. Resolution: Cannot Reproduce Closing per [~SteffenO]'s comment. See also [LOG4J2-1573]. > Log4j

[jira] [Comment Edited] (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=15492558#comment-15492558 ] Steffen Offermann edited comment on LOG4J2-1259 at 9/15/16 6:48 AM:

[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=15492558#comment-15492558 ] Steffen Offermann commented on LOG4J2-1259: --- @[~garydgregory]: In [comment

[jira] [Comment Edited] (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=15492558#comment-15492558 ] Steffen Offermann edited comment on LOG4J2-1259 at 9/15/16 6:48 AM:

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

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