Re: Jenkins build is still unstable: Log4j 2.x #2266

The Java 7 build works fine for me now. Ralph > On Sep 6, 2016, at 7:48 PM, Gary Gregory wrote: > > I do not get any failures running a local build on Java 8 with 'mvn clean > test'. I'll try Java 7... > > Gary > > -- Forwarded message -- > From:

Fwd: Jenkins build is still unstable: Log4j 2.x #2268

This looks like a filename case sensitivity issue. Pushed a fix. -- Forwarded message -- From: Apache Jenkins Server Date: 6 September 2016 at 23:48 Subject: Jenkins build is still unstable: Log4j 2.x #2268 To: log4j-dev@logging.apache.org See

Jenkins build is still unstable: Log4j 2.x #2268

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

[jira] [Comment Edited] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469444#comment-15469444 ] Matt Sicker edited comment on LOG4J2-1430 at 9/7/16 4:01 AM: - I was not aware

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469444#comment-15469444 ] Matt Sicker commented on LOG4J2-1430: - I was not aware of that feature. I'll try it out. > Add

Re: Local build Ok with Java 7 and 8

Built fine on Mac OS, Java 8. On 6 September 2016 at 22:08, Gary Gregory wrote: > I am using: > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; > 2015-11-10T08:41:47-08:00) > Maven home: E:\Java\apache-maven-3.3.9 > Java version: 1.7.0_79, vendor: Oracle

Re: logging-log4j2 git commit: Add changelog entries for LOG4J2-1430 and LOG4J2-1439

Good point. I'll add one tomorrow morning. On 6 September 2016 at 17:37, Remko Popma wrote: > It would be good to have a change log entry for the new TransferQueue > support in AsyncAppender. > > Sent from my iPhone > > > On 2016/09/07, at 6:56, mattsic...@apache.org

Jenkins build is still unstable: Log4j 2.x #2267

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

Local build Ok with Java 7 and 8

I am using: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00) Maven home: E:\Java\apache-maven-3.3.9 Java version: 1.7.0_79, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_79\jre Default locale: en_US, platform encoding: Cp1252 OS name:

Re: NullOutputStream.NULL_OUTPUT_STREAM;

Do we really need this kind of clutter in org.apache.logging.log4j.core.util? I'm doubtful... Gary On Sun, Sep 4, 2016 at 3:09 AM, Remko Popma wrote: > Can we deprecate and leave the old one in place after adding the new > constant? > > Sent from my iPhone > > On

Fwd: Jenkins build is still unstable: Log4j 2.x #2266

I do not get any failures running a local build on Java 8 with 'mvn clean test'. I'll try Java 7... Gary -- Forwarded message -- From: Apache Jenkins Server Date: Tue, Sep 6, 2016 at 10:38 PM Subject: Jenkins build is still unstable: Log4j 2.x #2266

Jenkins build is still unstable: Log4j 2.x #2266

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

[jira] [Resolved] (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:all-tabpanel ] Gary Gregory resolved LOG4J2-1563. -- Resolution: Fixed Fix Version/s: 2.7 In Git master. > Log4j 2.6.2 can lose exceptions

[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=15469276#comment-15469276 ] Gary Gregory commented on LOG4J2-1563: -- Hi, We now have: {code:java} try {

[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=15469270#comment-15469270 ] Gary Gregory commented on LOG4J2-1563: -- The tests restores the Security Manager, which is good.

[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=15469261#comment-15469261 ] Gary Gregory commented on LOG4J2-1563: -- The patch looks good. I'll apply it. Thank you. My next

Jenkins build is unstable: Log4j 2.x #2265

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

[jira] [Comment Edited] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469059#comment-15469059 ] Ralph Goers edited comment on LOG4J2-1430 at 9/7/16 12:24 AM: -- Thanks for

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469059#comment-15469059 ] Ralph Goers commented on LOG4J2-1430: - Thanks for doing this. I hate to nitpick though, but shouldn't

[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=15469033#comment-15469033 ] Gary Gregory edited comment on LOG4J2-1259 at 9/7/16 12:12 AM: --- I have a

[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=15469033#comment-15469033 ] Gary Gregory commented on LOG4J2-1259: -- I have a tentative fix that lets {{TriggeringPolicy}}

Re: Link to JAX Innovation Awards voting page from Log4j site?

FYI I'm thinking of doing this by directly modifying the HTML files under https://svn.apache.org/repos/infra/websites/production/logging/content/log4j/ so add (and remove) without dependency on our release schedule. On Wed, Sep 7, 2016 at 2:00 AM, Ralph Goers wrote:

Re: logging-log4j2 git commit: Add changelog entries for LOG4J2-1430 and LOG4J2-1439

It would be good to have a change log entry for the new TransferQueue support in AsyncAppender. Sent from my iPhone > On 2016/09/07, at 6:56, mattsic...@apache.org wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 97c09f1fe -> 7dd6d7ac8 > > > Add changelog

Re: Deprecated factory methods replaced by builders.

I think that would be good. Based on the number of Jira tickets being filed we are beginning to see increased uptake. Programmatic configuration is used surprisingly often. Leaving the factory methods in with some reasonable default for the missing parameters ensures existing users can

[jira] [Resolved] (LOG4J2-1439) Add optional support for JCTools in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1439. - Resolution: Fixed Code has been merged to master. > Add optional support for JCTools in

[jira] [Resolved] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1430. - Resolution: Fixed Code has been merged to master. > Add optional support for Conversant

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468740#comment-15468740 ] Matt Sicker commented on LOG4J2-1430: - Thanks, I've upgraded the dependency. > Add optional support

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

Alright, he's released a Java 7 version of the library. I'm testing it out now. This should fix the build issue. Users can override the library with the Java 8 version if they wish by excluding the JDK7 artifact and including the JDK8 one. On 6 September 2016 at 14:19, Matt Sicker

[jira] [Updated] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1086: - Summary: SizeBasedTriggeringPolicy is not working properly (was: SizeBasedTriggeringPolicy is

[jira] [Commented] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly with Logj2 2.3 version jars

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468581#comment-15468581 ] Eric Schwarzenbach commented on LOG4J2-1086: This is also broken in 2.6.2 . I suppose this is

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468568#comment-15468568 ] John Cairns commented on LOG4J2-1430: - I just uploaded a Java 7 repo to Nexus. Please try it with

[jira] [Comment Edited] (LOG4J2-1535) KafkaAppender NullPointerException when putting the related jars in tomcat lib

[ https://issues.apache.org/jira/browse/LOG4J2-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468545#comment-15468545 ] Bill Okara edited comment on LOG4J2-1535 at 9/6/16 9:00 PM: The issue has

[jira] [Comment Edited] (LOG4J2-1535) KafkaAppender NullPointerException when putting the related jars in tomcat lib

[ https://issues.apache.org/jira/browse/LOG4J2-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468545#comment-15468545 ] Bill Okara edited comment on LOG4J2-1535 at 9/6/16 8:59 PM: The issue has

Re: Inline org.apache.logging.log4j.core.util.Loader.loadClass(String)?

I in-lined the method and removed it from Core. Gary On Tue, Sep 6, 2016 at 1:10 AM, Matt Sicker wrote: > The core class is older than the api class. It was left there for a while > but can probably be pruned down. > > On 5 September 2016 at 16:36, Gary Gregory

[jira] [Created] (LOG4J2-1566) LevelRangeFilter default range has to be OFF->ALL

Andrey Plotkin created LOG4J2-1566: -- Summary: LevelRangeFilter default range has to be OFF->ALL Key: LOG4J2-1566 URL: https://issues.apache.org/jira/browse/LOG4J2-1566 Project: Log4j 2

Jenkins build is still unstable: Log4j 2.x #2263

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

[jira] [Commented] (LOG4J2-1565) PluginManager should be able to load plugins via SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468280#comment-15468280 ] Matt Sicker commented on LOG4J2-1565: - If you include a file named log4j2.component.properties on

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

Also, for the risk of using Java 8 library methods, that's the whole point of the animal-sniffer plugin. On 6 September 2016 at 14:01, Ralph Goers wrote: > I only run the release build using the compiler for the target release. > All the target option really does is

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

John is working on making a release that uses Java 1.7. On 6 September 2016 at 14:01, Ralph Goers wrote: > I only run the release build using the compiler for the target release. > All the target option really does is set the release version to the correct > value

[jira] [Updated] (LOG4J2-1565) PluginManager should be able to load plugins via SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Helger updated LOG4J2-1565: -- Description: I want to setup a custom configuration using a special factory class (based on

[jira] [Created] (LOG4J2-1565) PluginManager should be able to load plugins via SPI

Philip Helger created LOG4J2-1565: - Summary: PluginManager should be able to load plugins via SPI Key: LOG4J2-1565 URL: https://issues.apache.org/jira/browse/LOG4J2-1565 Project: Log4j 2

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468238#comment-15468238 ] Ralph Goers commented on LOG4J2-1430: - As I mentioned on the mailing list, we can't do a release

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

I only run the release build using the compiler for the target release. All the target option really does is set the release version to the correct value and verify you aren’t using language constructs from the newer java version. Using Java 8 with a target of Java 7 runs the risk that you

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468215#comment-15468215 ] Matt Sicker commented on LOG4J2-1430: - That would be helpful, yeah. > Add optional support for

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468176#comment-15468176 ] John Cairns commented on LOG4J2-1430: - [~jvz] If it comes to that I could do a one-off Java 7 build.

Re: Deprecated factory methods replaced by builders.

All the commits that removed deprecated factory methods it sounds like. On 6 September 2016 at 13:00, Gary Gregory wrote: > On Tue, Sep 6, 2016 at 12:31 PM, Matt Sicker wrote: > >> Should we revert those commits? There's still time. >> > > What commit?

Re: Deprecated factory methods replaced by builders.

On Tue, Sep 6, 2016 at 12:31 PM, Matt Sicker wrote: > Should we revert those commits? There's still time. > What commit? Do you mean to add back factory methods? Gary > > On 3 September 2016 at 01:12, Ralph Goers > wrote: > >> Perhaps we

Re: logging-log4j2 git commit: LOG4J2-1528 fix line endings

I saw a commit go by with an Assume, so that's good. Gary On Tue, Sep 6, 2016 at 11:48 AM, Mikael Ståldal wrote: > Like this? > > On Tue, Sep 6, 2016 at 4:51 PM, Gary Gregory > wrote: > >> Can you use a JUnit Assume to skip the test, that

Re: Link to JAX Innovation Awards voting page from Log4j site?

Go for it! Also, I believe it is letting you vote as many times as you want so long as it is from different ip addresses? If so, vote often! Ralph > On Sep 6, 2016, at 9:34 AM, Remko Popma wrote: > > I'm thinking to add a link to the JAX Innovation Awards voting page

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467880#comment-15467880 ] Leon Finker commented on LOG4J2-1457: - The fix is pretty simple either with patch attached, or as

[jira] [Closed] (LOG4J2-1530) LogEvent.getContextStack() can return null

[ https://issues.apache.org/jira/browse/LOG4J2-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1530. -- Problem solved. > LogEvent.getContextStack() can return null >

[jira] [Closed] (LOG4J2-1518) Deadlock when using pure async and toString logs another message

[ https://issues.apache.org/jira/browse/LOG4J2-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker closed LOG4J2-1518. --- > Deadlock when using pure async and toString logs another message >

Re: Deprecated factory methods replaced by builders.

That may be the simplest solution. We can think more on what to do with this in a subsequent release. On Wed, Sep 7, 2016 at 1:31 AM, Matt Sicker wrote: > Should we revert those commits? There's still time. > > On 3 September 2016 at 01:12, Ralph Goers

Link to JAX Innovation Awards voting page from Log4j site?

I'm thinking to add a link to the JAX Innovation Awards voting page from a number of pages on the Log4j site. Something like "Log4j 2 is nominated for the JAX Innovation Awards. Voting ends September 29, 2016. Please vote for Log4j 2 !" Thoughts? Remko

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

By that I mean they set their compiler version to 1.6 for src/main/ and 1.8 for src/test/ which shouldn't affect us as we're not using their test artifact. On 6 September 2016 at 11:22, Matt Sicker wrote: > JCTools requires 1.6 for the build and 1.8 for the test. It appears we

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

JCTools requires 1.6 for the build and 1.8 for the test. It appears we could do the same if the only thing failing the build is a unit test, but if the whole build is failing on Java 7, then I can back out those changes into a separate branch for future inclusion. On 6 September 2016 at 11:18,

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

Does JCTools require Java 8? One option is for this release to leave out the Conversant library and only include JCTools and the TransferQueue. On Wed, Sep 7, 2016 at 1:06 AM, Matt Sicker wrote: > I can't believe I didn't notice it, but the Conversant library does > require

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

Talking about that, it would be nice if the whole build process would work on Java 8, last time I tried the "site" goal did not work with Java 8. On Tue, Sep 6, 2016 at 6:06 PM, Matt Sicker wrote: > I can't believe I didn't notice it, but the Conversant library does > require

Re: [13/36] logging-log4j2 git commit: Convert BlockingQueueFactory into a plugin element

I can't believe I didn't notice it, but the Conversant library does require Java 8. It's an optional dependency, so what to do? We can build on Java 8 with a target for Java 7 and use the animal-sniffer Maven plugin to make sure we don't accidentally use anything from Java 8. On 5 September 2016

Re: logging-log4j2 git commit: LOG4J2-1528 fix line endings

Like this? On Tue, Sep 6, 2016 at 4:51 PM, Gary Gregory wrote: > Can you use a JUnit Assume to skip the test, that would allow that test to > be counted as skipped. > > Gary > > On Sep 6, 2016 5:46 AM, wrote: > >> Repository: logging-log4j2 >> Updated

[jira] [Resolved] (LOG4J2-1530) LogEvent.getContextStack() can return null

[ https://issues.apache.org/jira/browse/LOG4J2-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1530. Resolution: Fixed Fix Version/s: 2.7 Fixed in master. > LogEvent.getContextStack()

[jira] [Assigned] (LOG4J2-1530) LogEvent.getContextStack() can return null

[ https://issues.apache.org/jira/browse/LOG4J2-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1530: -- Assignee: Mikael Ståldal > LogEvent.getContextStack() can return null >

Jenkins build is still unstable: Log4j 2.x #2262

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

Re: logging-log4j2 git commit: LOG4J2-1528 fix line endings

Can you use a JUnit Assume to skip the test, that would allow that test to be counted as skipped. Gary On Sep 6, 2016 5:46 AM, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 170469514 -> 2f8236e5f > > > LOG4J2-1528 fix line endings > > >

[jira] [Commented] (LOG4J2-1530) LogEvent.getContextStack() can return null

[ https://issues.apache.org/jira/browse/LOG4J2-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467534#comment-15467534 ] Remko Popma commented on LOG4J2-1530: - I saw the commit mail and it looks fine. >

[jira] [Commented] (LOG4J2-1530) LogEvent.getContextStack() can return null

[ https://issues.apache.org/jira/browse/LOG4J2-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467518#comment-15467518 ] Mikael Ståldal commented on LOG4J2-1530: I have fixed it in branch LOG4J2-1530, can you review

[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=15467397#comment-15467397 ] Steffen Offermann edited comment on LOG4J2-1259 at 9/6/16 1:18 PM: --- The

[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=15467397#comment-15467397 ] Steffen Offermann commented on LOG4J2-1259: --- The problem is that the future holding the cron

[jira] [Resolved] (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 resolved LOG4J2-1528. Resolution: Fixed Production code should work as expected (please verify on Windows). Unit

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

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467261#comment-15467261 ] Mikael Ståldal edited comment on LOG4J2-1528 at 9/6/16 12:48 PM: - I have

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

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467261#comment-15467261 ] Mikael Ståldal edited comment on LOG4J2-1528 at 9/6/16 12:47 PM: - I have

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

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467261#comment-15467261 ] Mikael Ståldal commented on LOG4J2-1528: Then someone who use Windows have to change the {{EOL}}

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

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467249#comment-15467249 ] Remko Popma commented on LOG4J2-1528: - On Windows, the generated XML config files should really use

Jenkins build is still unstable: Log4j 2.x #2261

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

Jenkins build is still unstable: Log4j 2.x #2260

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466948#comment-15466948 ] Mikael Ståldal commented on LOG4J2-1528: So you think that we should produce XML config files

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

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466935#comment-15466935 ] Gary Gregory commented on LOG4J2-1528: -- There is still something wrong. It's not critical, but it's

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466930#comment-15466930 ] Remko Popma commented on LOG4J2-1457: - What is the status of this issue? > Class loader deadlock

[jira] [Comment Edited] (LOG4J2-1549) AsyncLoggerContextSelector+PropertiesConfigurationBuilder defaults to includeLocation=true

[ https://issues.apache.org/jira/browse/LOG4J2-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15464774#comment-15464774 ] Mikael Ståldal edited comment on LOG4J2-1549 at 9/6/16 9:02 AM:

[jira] [Created] (LOG4J2-1564) Java 9 compatibility

Remko Popma created LOG4J2-1564: --- Summary: Java 9 compatibility Key: LOG4J2-1564 URL: https://issues.apache.org/jira/browse/LOG4J2-1564 Project: Log4j 2 Issue Type: Epic Reporter:

Jenkins build is still unstable: Log4j 2.x #2259

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

[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=15466769#comment-15466769 ] Steffen Offermann edited comment on LOG4J2-1259 at 9/6/16 8:11 AM: ---

[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=15466627#comment-15466627 ] Steffen Offermann edited comment on LOG4J2-1259 at 9/6/16 8:10 AM: --- I

[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=15466772#comment-15466772 ] Steffen Offermann commented on LOG4J2-1259: --- Hmm, the pool thread stuff MIGHT be caused by a

[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=15466769#comment-15466769 ] Steffen Offermann commented on LOG4J2-1259: --- This (and the fact that the thread disappears once

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

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466756#comment-15466756 ] Mikael Ståldal commented on LOG4J2-1528: Are we fine with producing XML config files with \n line

[jira] [Commented] (LOG4J2-1530) LogEvent.getContextStack() can return null

[ https://issues.apache.org/jira/browse/LOG4J2-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466746#comment-15466746 ] Mikael Ståldal commented on LOG4J2-1530: Reproduce by using Log4j1XmlLayout or

Re: Thread management clean ups

YW ;-) Gary On Tue, Sep 6, 2016 at 2:48 AM, Remko Popma wrote: > Thank you! It is good to know the background of why some of these changes > are happening. > > Sent from my iPhone > > On 2016/09/06, at 10:13, Gary Gregory wrote: > > Hi All, > > I

Re: Git commit

That would be nice. On Tue, Sep 6, 2016 at 6:17 AM, Gary Gregory wrote: > Yes indeed, that's how I've used FishEye + Jira at work. > > Gary > > On Mon, Sep 5, 2016 at 11:48 PM, Matt Sicker wrote: > >> That works as long as you include the ticket number

[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=15466640#comment-15466640 ] Steffen Offermann commented on LOG4J2-1259: --- Oh, and I just noticed that the following threads

Re: Thread management clean ups

Thank you! It is good to know the background of why some of these changes are happening. Sent from my iPhone > On 2016/09/06, at 10:13, Gary Gregory wrote: > > Hi All, > > I am continuing some thread management clean ups. > > We use a couple of thread pools here and

[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=15466625#comment-15466625 ] Gary Gregory commented on LOG4J2-1259: -- If you add our SNAPSHOT repository to your Maven settings,

[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=15466627#comment-15466627 ] Steffen Offermann commented on LOG4J2-1259: --- I was able to do a local build, and the result

[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=15466557#comment-15466557 ] Steffen Offermann commented on LOG4J2-1259: --- Hi, Gary! No, I used the latest release, 2.6.2,