Re: ExecutorService.shutdown

> On Jan 10, 2017, at 2:09 PM, Mikael Ståldal wrote: > > It seems like ExecutorService.shutdown invokes executorService.shutdown() > twice If timeout is 0. Is this correct? A) Do you mean ExecutorServices? I don’t see any code that calls shutdown() twice. I do see code that calls shutdown() f

Re: Github integration set up: logging--log4j-boot.git

Yeah, that's a duplicate anyhow. The correctly named one is where I've added a few files. On 10 January 2017 at 20:30, Gary Gregory wrote: > That repo name is not right :-( > > G > > -- Forwarded message -- > From: > Date: Tue, Jan 10, 2017 at 6:30 PM > Subject: Github integrati

Fwd: Github integration set up: logging--log4j-boot.git

That repo name is not right :-( G -- Forwarded message -- From: Date: Tue, Jan 10, 2017 at 6:30 PM Subject: Github integration set up: logging--log4j-boot.git To: infrastruct...@apache.org, priv...@logging.apache.org New repository logging--log4j-boot.git has now had GitHub int

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816578#comment-15816578 ] Gary Gregory commented on LOG4J2-1748: -- Yep, IIRC, that is why I did it that way. >

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816488#comment-15816488 ] Remko Popma commented on LOG4J2-1748: - I believe (I could be wrong) that the non-daem

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

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-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816297#comment-15816297 ] Ralph Goers commented on LOG4J2-1640: - Yes, you would need to re-clone and re-build.

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816237#comment-15816237 ] Chris McGee commented on LOG4J2-1640: - Wow, a lot of new info to take in. I don't ful

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816238#comment-15816238 ] Gary Gregory commented on LOG4J2-1780: -- What I think we need to consider here is if

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816212#comment-15816212 ] Mikael Ståldal commented on LOG4J2-1780: Ping [~garydgregory] > LoggerContext do

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816208#comment-15816208 ] Mikael Ståldal commented on LOG4J2-1748: Created a bug for the failure to shut do

[jira] [Created] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

Mikael Ståldal created LOG4J2-1780: -- Summary: LoggerContext does not shut down old executor services when creating new ones during reconfiguration Key: LOG4J2-1780 URL: https://issues.apache.org/jira/browse/LOG4J

ExecutorService.shutdown

It seems like ExecutorService.shutdown invokes executorService.shutdown() twice If timeout is 0. Is this correct?

[jira] [Comment Edited] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816150#comment-15816150 ] Mikael Ståldal edited comment on LOG4J2-1748 at 1/10/17 9:01 PM: --

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816150#comment-15816150 ] Mikael Ståldal commented on LOG4J2-1748: I am not sure that it will be dangerous

[jira] [Closed] (LOG4J2-1762) Add Builder to GelfLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1762. -- > Add Builder to GelfLayout > - > > Key: LOG4J2-1762 >

Fwd: logging-log4j2 git commit: LOG4J2-1243 - Allow default value in property to be a Lookup.

-- Forwarded message -- From: Date: Tue, Jan 10, 2017 at 7:38 AM Subject: logging-log4j2 git commit: LOG4J2-1243 - Allow default value in property to be a Lookup. To: comm...@logging.apache.org Repository: logging-log4j2 Updated Branches: refs/heads/master ba4822b1c -> 0c2c11db

Fwd: logging-log4j2 git commit: Fix failing unit test

Our JUnit rule org.apache.logging.log4j.junit.CleanFiles would come in handy here. Gary -- Forwarded message -- From: Date: Tue, Jan 10, 2017 at 7:17 AM Subject: logging-log4j2 git commit: Fix failing unit test To: comm...@logging.apache.org Repository: logging-log4j2 Updated B

[jira] [Closed] (LOG4J2-1769) JsonLayout Throwing Exceptions And Producing Broken Logs

[ https://issues.apache.org/jira/browse/LOG4J2-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Goodin closed LOG4J2-1769. -- This is indeed fixed in the 2.7.1 SNAPSHOT. > JsonLayout Throwing Exceptions And Producing Broken

[jira] [Commented] (LOG4J2-1769) JsonLayout Throwing Exceptions And Producing Broken Logs

[ https://issues.apache.org/jira/browse/LOG4J2-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815651#comment-15815651 ] Brandon Goodin commented on LOG4J2-1769: I tested against 2.7.1-SNAPSHOT on Janua

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

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

Re: [1/2] logging-log4j2 git commit: Fixed concurrency issue affecting all layouts except PatternLayout and GelfLayout, which caused scrambled output and exceptions when logging synchronously from mul

Ouch! Thank you! On Wed, Jan 11, 2017 at 12:16 AM, Apache wrote: > Yes, it passes on your Windows machine. > > The test was creating the LoggerContext and configuration before the > @Before code is run. The before method attempts to delete the file. On > Windows that will fail because the file i

Re: [1/2] logging-log4j2 git commit: Fixed concurrency issue affecting all layouts except PatternLayout and GelfLayout, which caused scrambled output and exceptions when logging synchronously from mul

Yes, it passes on your Windows machine. The test was creating the LoggerContext and configuration before the @Before code is run. The before method attempts to delete the file. On Windows that will fail because the file is open. On unix the file’s directory entry will be deleted but the file ou

[jira] [Closed] (LOG4J2-1779) AsyncLogger does not lookup properties

[ https://issues.apache.org/jira/browse/LOG4J2-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1779. --- > AsyncLogger does not lookup properties > -- > > Key

[jira] [Resolved] (LOG4J2-1779) AsyncLogger does not lookup properties

[ https://issues.apache.org/jira/browse/LOG4J2-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1779. - Resolution: Fixed Fixed in commit a686a4e. > AsyncLogger does not lookup properties > --

[jira] [Created] (LOG4J2-1779) AsyncLogger does not lookup properties

Remko Popma created LOG4J2-1779: --- Summary: AsyncLogger does not lookup properties Key: LOG4J2-1779 URL: https://issues.apache.org/jira/browse/LOG4J2-1779 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815008#comment-15815008 ] Alexander K. commented on LOG4J2-1724: -- It works as expected. Thanks. > Using varia

[jira] [Closed] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander K. closed LOG4J2-1724. > Using variables in GelfLayout's additional fields at runtime > --

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814716#comment-15814716 ] Mikael Ståldal commented on LOG4J2-1748: After looking more closely at this, I th

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814711#comment-15814711 ] Mikael Ståldal commented on LOG4J2-1748: A simple workaround is to add System.exi

JDK 9 EA Build 151 is available on java.net

Hi Nick, Best wishes for the New Year. Dalibor and I will be at FOSDEM '17, Brussels 4 & 5 February. Let us know if you will be there, hopefully we can meet up ! *JDK 9 Early Access* b151 is available on java.net There have been a number of fixes to bugs