[jira] [Updated] (LOG4J2-794) configurationFile with space in name will fail to be loaded

[ https://issues.apache.org/jira/browse/LOG4J2-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-794: --- Description: We've set the System Property "log4j.configurationFile" to be {{"C:\\Repo\\Metrix

Early Access build for JDK 9 b27 is available on java.net

Hi Nick, Early Access build for JDK 9 b27 is available on java.net, summary of changes here I'd also like to use this opportunity to point you to ongoing work in OpenJDK on Project Jigsaw. - JD

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106656#comment-14106656 ] Remko Popma commented on LOG4J2-658: Romain, can I clarify again what you are trying t

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106727#comment-14106727 ] Romain Manni-Bucau commented on LOG4J2-658: --- Well my goal was larger than this i

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106792#comment-14106792 ] Remko Popma commented on LOG4J2-658: Oh! Async logging in log4j2 auto-flushes when the

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106903#comment-14106903 ] Romain Manni-Bucau commented on LOG4J2-658: --- Well regarding TomEE we'll not use

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106917#comment-14106917 ] Remko Popma commented on LOG4J2-658: Async loggers and the async appender will flush w

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107116#comment-14107116 ] Romain Manni-Bucau commented on LOG4J2-658: --- [~rem...@yahoo.com] can you point m

[jira] [Commented] (LOG4J2-789) Where can I view the embedded flume agent startup logs

[ https://issues.apache.org/jira/browse/LOG4J2-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107151#comment-14107151 ] Bijith Kumar commented on LOG4J2-789: - Hi Ralph, Thanks. I doubt that it is using defa

[jira] [Commented] (LOG4J2-789) Where can I view the embedded flume agent startup logs

[ https://issues.apache.org/jira/browse/LOG4J2-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107203#comment-14107203 ] Ralph Goers commented on LOG4J2-789: As I said, the log level in the default configura

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107230#comment-14107230 ] Romain Manni-Bucau commented on LOG4J2-658: --- Hmm checked on the jvm i use (1.7.

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107232#comment-14107232 ] Matt Sicker commented on LOG4J2-658: That's why I started that shutdown strategy class

[ANN] Apache Log4j 2.0.2 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.0.2 release! Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many of the improvements available in

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107367#comment-14107367 ] Romain Manni-Bucau commented on LOG4J2-658: --- @Matt it is fine for me while it wo

[jira] [Created] (LOG4J2-795) Problems when libraries are loaded as part of server startup classpath

Mike Calmus created LOG4J2-795: -- Summary: Problems when libraries are loaded as part of server startup classpath Key: LOG4J2-795 URL: https://issues.apache.org/jira/browse/LOG4J2-795 Project: Log4j 2

Could use some help prodding INFRA to get us on git.

https://issues.apache.org/jira/browse/INFRA-8169 -- Matt Sicker

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107561#comment-14107561 ] Remko Popma commented on LOG4J2-658: I still think that the simplest thing is to not r

Re: Log4j 2 vs. Commons Logging

Have you asked this on the commons mailing list? On 20 August 2014 09:46, Matt Sicker wrote: > I'd certainly say so. Commons Logging doesn't have parameterized messages > or markers; that's a pretty big feature at this point. > > > On 20 August 2014 08:42, Gary Gregory wrote: > >> Hi All, >> >

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107568#comment-14107568 ] Matt Sicker commented on LOG4J2-658: I still think the main idea to take from this is

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107608#comment-14107608 ] Gary Gregory commented on LOG4J2-658: - It seems like the simplest solution for now wou

Re: Could use some help prodding INFRA to get us on git.

I’ve never had much luck with prodding Infra. Ralph On Aug 22, 2014, at 2:42 PM, Matt Sicker wrote: > https://issues.apache.org/jira/browse/INFRA-8169 > > -- > Matt Sicker

Re: Log4j 2 vs. Commons Logging

I do not think it matters from the Commons POV. I am the Commons PMC Chair FYI. Commons as a community can think and do what it wants with Commons Logging. What I am more concerned about is if, we, the Log4j Community can say with confidence "Log4j 2 is so good that we consider Commons Logging obso

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107660#comment-14107660 ] Ralph Goers commented on LOG4J2-658: Things like the HTMLLayout, XMLLayout, or JSONLay

Re: Log4j 2 vs. Commons Logging

With SLF4J, JCL, and Log4j1 compatibility, I think we're far better than JCL. I think we need a proper java.util.logger bridge as well to be a complete replacement, though. On 22 August 2014 18:08, Gary Gregory wrote: > I do not think it matters from the Commons POV. I am the Commons PMC Chair

Re: Log4j 2 vs. Commons Logging

On Fri, Aug 22, 2014 at 7:12 PM, Matt Sicker wrote: > With SLF4J, JCL, and Log4j1 compatibility, I think we're far better than > JCL. I think we need a proper java.util.logger bridge as well to be a > complete replacement, though. > I agree there, a bridge would round things out. For 2.1? Gary

Re: Log4j 2 vs. Commons Logging

That was my goal at least with the work I did a little while back. Though simplifying the requirements to making the user specify the correct system property to choose Log4j2 does make that a whole lot easier. On 22 August 2014 18:17, Gary Gregory wrote: > On Fri, Aug 22, 2014 at 7:12 PM, Matt

[jira] [Commented] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107832#comment-14107832 ] Ian Barfield commented on LOG4J2-741: - This change has made 2.0.1+ unusable for me. It

[jira] [Comment Edited] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107832#comment-14107832 ] Ian Barfield edited comment on LOG4J2-741 at 8/23/14 3:27 AM: --

[jira] [Commented] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107836#comment-14107836 ] Jed Wesley-Smith commented on LOG4J2-741: - @ianbarfield OOI, do you specify a "pac

[jira] [Updated] (LOG4J2-766) Incomplete documentation for JSONLayout

[ https://issues.apache.org/jira/browse/LOG4J2-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno P. Kinoshita updated LOG4J2-766: -- Attachment: LOG4J-766-1.png LOG4J2-766.patch Patch that includes a tabl

Re: Log4j 2 vs. Commons Logging

Could we set this property ourselves in the JUL bridge jar? So that just including this jar would set the system property? (Just thinking out loud...) Sent from my iPhone > On 2014/08/23, at 3:44, Matt Sicker wrote: > > That was my goal at least with the work I did a little while back. Though

[jira] [Commented] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107871#comment-14107871 ] Remko Popma commented on LOG4J2-741: Ian, we can definitely look into this. Would you

[jira] [Commented] (LOG4J2-658) shutdown hook called too early

[ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107875#comment-14107875 ] Remko Popma commented on LOG4J2-658: I actually think its fine the way it is since app