[jira] [Closed] (LOG4J2-1114) Add thread name to status logger layout

[ https://issues.apache.org/jira/browse/LOG4J2-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1114. Resolution: Fixed In Git master. > Add thread name to status logger layout > -

Re: Release status

Done; in Git master. Gary On Mon, Sep 7, 2015 at 9:21 PM, Ralph Goers wrote: > I have no objections if there is no serious impact to performance. > > Ralph > > On Sep 7, 2015, at 9:20 PM, Gary Gregory wrote: > > I am finding that the lack of thread name in the status logger is not > helping my

Re: Release status

Very fast, thank you! Would you mind also fixing the broken link to the January Mulesoft blog post? > broken link: > http://blogs.mulesoft.org/mule-3-6-asynchronous-logging/ > new link is: > http://blogs.mulesoft.com/dev/mule-dev/mule-3-6-asynchronous-logging/ > Sent from my iPhone > On

[jira] [Updated] (LOG4J2-1114) Add thread name to status logger layout

[ https://issues.apache.org/jira/browse/LOG4J2-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1114: - Description: Add thread name to status logger layout. Right status logging looks like this: {nof

[jira] [Created] (LOG4J2-1114) Add thread name to status logger layout

Gary Gregory created LOG4J2-1114: Summary: Add thread name to status logger layout Key: LOG4J2-1114 URL: https://issues.apache.org/jira/browse/LOG4J2-1114 Project: Log4j 2 Issue Type: Improve

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734257#comment-14734257 ] Ralph Goers commented on LOG4J2-1010: - I took a brief look at the patch and nothing o

Re: Release status

I have no objections if there is no serious impact to performance. Ralph > On Sep 7, 2015, at 9:20 PM, Gary Gregory wrote: > > I am finding that the lack of thread name in the status logger is not helping > my debugging. > > Any thoughts against adding the thread name? > > Gary > > On Mon

Re: Release status

I am finding that the lack of thread name in the status logger is not helping my debugging. Any thoughts against adding the thread name? Gary On Mon, Sep 7, 2015 at 9:13 PM, Ralph Goers wrote: > I still have to fix the problem with liquibase not appearing in the site. > I doubt I will have tim

Re: Log4j 1 web site

I don’t believe anyone has taken care of this. How is the log4j 1 site built? I don’t remember. Ralph > On Aug 22, 2015, at 7:56 AM, Gary Gregory wrote: > > For sure, and point to the v 2 site. > > Gary > > > Original message > From: Ralph Goers > Date: 08/21/2015 23:22

Re: Release status

I still have to fix the problem with liquibase not appearing in the site. I doubt I will have time until later in the week to do the release build as I do most of my checking before I create the release candidate. Ralph > On Sep 7, 2015, at 9:04 PM, Gary Gregory wrote: > > I'd like to get my

Re: Release status

Thanks for reviewing! I have fixed all of these. Ralph > On Sep 7, 2015, at 6:55 PM, Remko Popma wrote: > > Agree that LOG4J2-1102 is not a blocker. > > Nitpicking & new articles below (can't commit from work, can do this tonight): > > customconfig.xml > line 38: ">" should be "" > line 110:

Re: Release status

I'd like to get my ZeroMQ appender working for 2.4 but I am having a heck of a time getting rid of tricky threading issues. It should not hold up a release of course. Gary On Mon, Sep 7, 2015 at 7:13 PM, Ralph Goers wrote: > Yeah. Didn’t see the point of having two PropertiesUtil classes. > > R

Re: Release status

Yeah. Didn’t see the point of having two PropertiesUtil classes. Ralph > On Sep 7, 2015, at 6:49 PM, Gary Gregory wrote: > > Oh... I need to reinstall the log4j-api module... > > On Mon, Sep 7, 2015 at 6:47 PM, Gary Gregory > wrote: > I get a few: > > The metho

Re: Release status

Agree that LOG4J2-1102 is not a blocker. Nitpicking & new articles below (can't commit from work, can do this tonight): customconfig.xml line 38: ">" should be "" line 110: add 4 spaces indentation line 112: add 4 spaces indentation line 148: "cofigured" should be "configured" line 149: "it does

Re: Release status

Oh... I need to reinstall the log4j-api module... On Mon, Sep 7, 2015 at 6:47 PM, Gary Gregory wrote: > I get a few: > > The method extractSubset(Properties, String) is undefined for the type > PropertiesUtil. > > Gary > > On Mon, Sep 7, 2015 at 5:58 PM, Ralph Goers > wrote: > >> I have merged

Re: Release status

I get a few: The method extractSubset(Properties, String) is undefined for the type PropertiesUtil. Gary On Mon, Sep 7, 2015 at 5:58 PM, Ralph Goers wrote: > I have merged the LOG4J2-952 branch and added documentation as well as > made a few other minor changes. > > I have built the site and n

Re: Release status

Hi Ralph, You've already mentioned LOG4J2-1102 so that should be it. I'll take a look at the merged branch and new docs starting tomorrow night hopefully. Gary On Mon, Sep 7, 2015 at 5:58 PM, Ralph Goers wrote: > I have merged the LOG4J2-952 branch and added documentation as well as > made a

Release status

I have merged the LOG4J2-952 branch and added documentation as well as made a few other minor changes. I have built the site and noticed that the Liquibase sub-project is not showing up. I think there is something wrong with the site descriptor and will investigate that. I started working on L

[jira] [Resolved] (LOG4J2-635) Log4j 2 should also support properties file

[ https://issues.apache.org/jira/browse/LOG4J2-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-635. Resolution: Fixed As part of LOG4J2-952 support for properties files was added. Please verify and c

[jira] [Resolved] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-952. Resolution: Fixed Fix Version/s: 2.4 Branch LOG4J2-952 has been merged to master. Please veri

[jira] [Commented] (LOG4J2-1113) Create new publisher Appender for ZeroMQ (using JeroMQ)

[ https://issues.apache.org/jira/browse/LOG4J2-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734065#comment-14734065 ] Ralph Goers commented on LOG4J2-1113: - JeroMQ is licensed under the LGPL. Please make

[jira] [Created] (LOG4J2-1113) Create new publisher Appender for ZeroMQ (using JeroMQ)

Gary Gregory created LOG4J2-1113: Summary: Create new publisher Appender for ZeroMQ (using JeroMQ) Key: LOG4J2-1113 URL: https://issues.apache.org/jira/browse/LOG4J2-1113 Project: Log4j 2 Iss

Re: LogEvent time API inconsistency

Right, I figured as much, but it does not look as nice as much it could be... Gary On Mon, Sep 7, 2015 at 3:46 AM, Remko Popma wrote: > I deliberately chose that name to be consistent with the data source > (System::nanoTime). > > As to why System::nanoTime is apparently not consistent with > S

[jira] [Commented] (LOG4J2-1088) Add Comma Separated Value (CSV) layouts for parameter and event logging.

[ https://issues.apache.org/jira/browse/LOG4J2-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733758#comment-14733758 ] Gary Gregory commented on LOG4J2-1088: -- Good and valid points, Remko. Thank you. I'v

[jira] [Commented] (LOG4J2-1088) Add Comma Separated Value (CSV) layouts for parameter and event logging.

[ https://issues.apache.org/jira/browse/LOG4J2-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733568#comment-14733568 ] Remko Popma commented on LOG4J2-1088: - Async Loggers and Async Appenders will call Me

Re: LogEvent time API inconsistency

I deliberately chose that name to be consistent with the data source (System::nanoTime). As to why System::nanoTime is apparently not consistent with System::currentTimeMillis, I suspect the Sun/Oracle engineers did this on purpose to avoid giving the impression that System::nanoTime had anything

[jira] [Closed] (LOG4J2-1088) Add Comma Separated Value (CSV) layouts for parameter and event logging.

[ https://issues.apache.org/jira/browse/LOG4J2-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1088. Resolution: Fixed In Git master. > Add Comma Separated Value (CSV) layouts for parameter and event

[jira] [Updated] (LOG4J2-1088) Add Comma Separated Value (CSV) layouts for parameter and event logging.

[ https://issues.apache.org/jira/browse/LOG4J2-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1088: - Summary: Add Comma Separated Value (CSV) layouts for parameter and event logging. (was: Add a Co

LogEvent time API inconsistency

Hi All: In org.apache.logging.log4j.core.LogEvent, we have two timestamp getters: - getNanoTime() (new 2.4) - getTimeMillis() The naming is inconsistent, I propose to change getNanoTime() to getTimeNanos(). Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persisten