[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431923#comment-15431923 ] Ralph Goers commented on LOG4J2-1539: - Yes. As I said, I am afraid getContext() might not always

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431898#comment-15431898 ] Ralph Goers commented on LOG4J2-1539: - As soon as you need the LoggerContext in the Managers it opens

Re: 35 items in changes.xml since release 2.6.2 on July 5!

I’m sure I have stuff I want to do. It just isn’t going to get done this week. The soonest I could target doing a release would be labor day weekend. But I expect I will probably spend most of that addressing issues I’ve been trying to get to. Ralph > On Aug 22, 2016, at 5:32 PM, Gary Gregory

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431822#comment-15431822 ] Ralph Goers commented on LOG4J2-1539: - I dislike the patch because of the call

[jira] [Commented] (LOG4J2-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431300#comment-15431300 ] Ralph Goers commented on LOG4J2-1349: - Hmmm. "now that LogEvents use ContextData...".

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like Camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430613#comment-15430613 ] Ralph Goers commented on LOG4J2-905: We have no plans to do that as this should give you exactly what

Re: Component vs. Node

> On Aug 21, 2016, at 4:30 AM, Mikael Ståldal wrote: > > Why does the ConfigurationBuilder uses its own Component class rather than > Node? They looks very similar to me. > Yes, they are very similar. But you will notice that the Node has a reference to its

[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=15429796#comment-15429796 ] Ralph Goers commented on LOG4J2-1528: - Is there a test for that? If not, add one and find out

Re: Close Input Stream in Configuration factory?

Almost certainly. Sent from my iPad > On Aug 21, 2016, at 3:40 AM, Mikael Ståldal wrote: > > Is a ConfigurationFactory that uses the InputStream from the > ConfigurationSource supposed to close the stream when done? It seems like > XmlConfigurationFactory,

[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=15429765#comment-15429765 ] Ralph Goers commented on LOG4J2-1528: - I am pretty sure that is not true. The locarion information

[jira] [Commented] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429763#comment-15429763 ] Ralph Goers commented on LOG4J2-1531: - Ok. Then I will do it when I get some time. > Cha

[jira] [Assigned] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1531: --- Assignee: Ralph Goers > Change attribute and component values from String to Obj

[jira] [Comment Edited] (LOG4J2-1537) Experience of a newbie to logging

[ https://issues.apache.org/jira/browse/LOG4J2-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429501#comment-15429501 ] Ralph Goers edited comment on LOG4J2-1537 at 8/20/16 8:17 PM: -- Please see

[jira] [Commented] (LOG4J2-1537) Experience of a newbie to logging

[ https://issues.apache.org/jira/browse/LOG4J2-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429501#comment-15429501 ] Ralph Goers commented on LOG4J2-1537: - Please see http://logging.apache.org/log4j/2.x/runtime

[jira] [Commented] (LOG4J2-1522) Log4j 1 layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429497#comment-15429497 ] Ralph Goers commented on LOG4J2-1522: - I have mixed feelings about this. Conceptually they do belong

[jira] [Commented] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429494#comment-15429494 ] Ralph Goers commented on LOG4J2-1531: - If you do the above you have to allow arbitrary objects

Re: ThreadContextMap2

gt; Fair enough. > > I am wondering if there is a design reason not to implement Map now that we > have the opportunity with the TCM2 interface. I'd take a crack at it. > > Gary > > > On Aug 20, 2016 10:39 AM, "Ralph Goers" <ralph.go...@dslextreme.com >

Re: ThreadContextMap2

Because Map has a lot more methods that weren’t needed and I didn’t want to implement? Ralph > On Aug 20, 2016, at 10:16 AM, Gary Gregory wrote: > > Hi All: > > Now that we have ThreadContextMap2: > > Why don't we do ThreadContextMap2 extends Map? >

[jira] [Comment Edited] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429453#comment-15429453 ] Ralph Goers edited comment on LOG4J2-1531 at 8/20/16 5:35 PM: -- I like what

[jira] [Commented] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429455#comment-15429455 ] Ralph Goers commented on LOG4J2-1531: - Mikael,I don't know that I would want to move

[jira] [Commented] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429453#comment-15429453 ] Ralph Goers commented on LOG4J2-1531: - I like what this patch is trying to do, however, I have some

[jira] [Commented] (LOG4J2-1529) composite configurations do not merge attributes on logger nodes

[ https://issues.apache.org/jira/browse/LOG4J2-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429219#comment-15429219 ] Ralph Goers commented on LOG4J2-1529: - And feel free to create patches for other issues that interest

[jira] [Commented] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428352#comment-15428352 ] Ralph Goers commented on LOG4J2-1531: - Can you create a patch for this? I'd prefer to look

Re: [site] Legacy section

Why? Log4j 2.3 is significant as it is the last release to support Java 6 and Log4j 1.2 is, of course, the last (and only) link to log4j 1. If we link to all then we would have 20 links there and it wouldn’t be obvious that log4j 2.3 was the last to support Java 6. Ralph > On Aug 18, 2016,

[jira] [Issue Comment Deleted] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-905: --- Comment: was deleted (was: Hi I'm out of office until September 19th and I will not respond to my

[jira] [Comment Edited] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426860#comment-15426860 ] Ralph Goers edited comment on LOG4J2-905 at 8/18/16 5:39 PM: - IMO, the correct

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426860#comment-15426860 ] Ralph Goers commented on LOG4J2-905: IMO, the correct solution is to add an option to %msg

Re: Migrating from Log4j 1

Neither of those imply that the conversion has to be at runtime. My concern here is that any conversion is unlikely to be 100% compatible, so providing a tool that creates a new configuration that you can then use and modify seems like a better way to go. It is also pretty much what Logback

[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=15425621#comment-15425621 ] Ralph Goers commented on LOG4J2-1528: - True. I personally prefer XML over JSON for the Log4j

[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=15425301#comment-15425301 ] Ralph Goers commented on LOG4J2-1528: - I'll take a look but probably won't get a chance until

[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=15425283#comment-15425283 ] Ralph Goers commented on LOG4J2-1528: - LOG4J2-1525 should not be dependent

[jira] [Commented] (LOG4J2-1524) Support overall structure of Log4j 1 log4j.properties

[ https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425279#comment-15425279 ] Ralph Goers commented on LOG4J2-1524: - I didn't mean to imply that a Log4j 1 configuration would

[jira] [Commented] (LOG4J2-1522) Log4j 1 layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425054#comment-15425054 ] Ralph Goers commented on LOG4J2-1522: - TTCC_CONVERSION_PATTERN is a static constant

[jira] [Commented] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425033#comment-15425033 ] Ralph Goers commented on LOG4J2-1526: - It is an oversight. It should be added. > Possibility to

[jira] [Commented] (LOG4J2-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[ https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424878#comment-15424878 ] Ralph Goers commented on LOG4J2-1525: - I am confused. XMLLayout started from the Log4j 1 XMLLayout

[jira] [Commented] (LOG4J2-1524) Support overall structure of Log4j 1 log4j.properties

[ https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424859#comment-15424859 ] Ralph Goers commented on LOG4J2-1524: - While that may be true from a technical point of view, we

[jira] [Commented] (LOG4J2-1524) Support overall structure of Log4j 1 log4j.properties

[ https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424588#comment-15424588 ] Ralph Goers commented on LOG4J2-1524: - I am not crazy about doing this at run time. I prefer

[jira] [Commented] (LOG4J2-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[ https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424586#comment-15424586 ] Ralph Goers commented on LOG4J2-1525: - If a meta-data file can be provided that maps Log4j 1

[jira] [Commented] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424577#comment-15424577 ] Ralph Goers commented on LOG4J2-1523: - a) Why do we want to do this? b) How can this be done? Log4j

[jira] [Commented] (LOG4J2-1522) Log4j 1 layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424576#comment-15424576 ] Ralph Goers commented on LOG4J2-1522: - a) Why do we want to do this? b) How can this be done? Log4j

[jira] [Commented] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421353#comment-15421353 ] Ralph Goers commented on LOG4J2-1517: - I'm fine with the "one at a time' method. If there was

[jira] [Commented] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420610#comment-15420610 ] Ralph Goers commented on LOG4J2-1517: - I also have concerns about this. I'd really need to understand

Re: Migrating from Log4j 1

> > Sent from my iPhone > > On 2016/08/13, at 9:59, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > >> That’s the same thing SLF4J did - See http://slf4j.org/faq.html#excludingJCL >> <http://slf4j.org/faq.ht

Re: Migrating from Log4j 1

gt;> Not sure about #2 and #3. >> >> Remko >> >> >> Sent from my iPhone >> >> On 2016/08/13, at 7:38, Matt Sicker <boa...@gmail.com >> <mailto:boa...@gmail.com>> wrote: >> >>> Yeah, really, what's the altern

[jira] [Commented] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419583#comment-15419583 ] Ralph Goers commented on LOG4J2-1512: - Log4j 1 and Logback both always swallowed exceptions

Re: Migrating from Log4j 1

Dropping Log4j 1 and doing what instead? Stop logging altogether? Logback’s configuration isn’t compatible either. Ralph > On Aug 12, 2016, at 9:52 AM, Mikael Ståldal wrote: > > There seem to be quite some frustration in some other Apache projects about >

[jira] [Commented] (LOG4J2-1501) FileAppender should be able to create files lazily

[ https://issues.apache.org/jira/browse/LOG4J2-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412389#comment-15412389 ] Ralph Goers commented on LOG4J2-1501: - I will take a peek as soon as I can. > FileAppender sho

[jira] [Commented] (LOG4J2-1501) FileAppender should be able to create files lazily

[ https://issues.apache.org/jira/browse/LOG4J2-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412388#comment-15412388 ] Ralph Goers commented on LOG4J2-1501: - I haven't had a chance to read the documentation that Matt put

[jira] [Commented] (LOG4J2-1501) FileAppender should be able to create files lazily

[ https://issues.apache.org/jira/browse/LOG4J2-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412385#comment-15412385 ] Ralph Goers commented on LOG4J2-1501: - There is no need for backward compatibility. > FileAppen

[jira] [Commented] (LOG4J2-1501) FileAppender should be able to create files lazily

[ https://issues.apache.org/jira/browse/LOG4J2-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412056#comment-15412056 ] Ralph Goers commented on LOG4J2-1501: - Please explain why you deprecated the existing createAppender

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

Ralph’s rule #1: Don’t trust your IDE: Always run the Maven build from the command line. Ralph > On Aug 5, 2016, at 12:09 PM, Gary Gregory wrote: > > Frak! XmlCompleteFileAppenderTest works fine from Eclipse... > > On Fri, Aug 5, 2016 at 11:54 AM, Matt Sicker

[jira] [Commented] (LOG4J2-1448) Allow comma separated agents, host list to be passed to FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408963#comment-15408963 ] Ralph Goers commented on LOG4J2-1448: - If Matt isn't comfortable with it I will try to get

Re: Log4j Scala API

I have been swamped at work. It will take me a couple of days to look at this. Ralph > On Aug 3, 2016, at 4:43 AM, Mikael Ståldal wrote: > > I think that the Scala API I have been working on for quite long is ready now. > > Any objections to merging the branch

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

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399866#comment-15399866 ] Ralph Goers commented on LOG4J2-1010: - What difference does that make? The lookup has always gotten

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

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399507#comment-15399507 ] Ralph Goers commented on LOG4J2-1010: - That is unnecessary. The ContextMapLookup should be getting

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

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399501#comment-15399501 ] Ralph Goers commented on LOG4J2-1010: - As you stated, when a LogEvent has not been created a Filter

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399495#comment-15399495 ] Ralph Goers commented on LOG4J2-1447: - Lookups can be used in places where a LogEvent does not exist

Re: Build failed in Jenkins: Log4j 2.x #2108

Done Ralph > On Jul 28, 2016, at 5:59 PM, Matt Sicker wrote: > > Hooray, it looks like infra is testing yet another broken Jenkins environment > on us! Can we filter this one out, too? > > On 28 July 2016 at 19:41, Apache Jenkins Server

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

least have a documented opinion on JDNI, j.u.prefs, and anything else like > Commons Configuration. > > Gary > > On Tue, Jul 26, 2016 at 12:58 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > The configuration for JDBC is

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

ou usually can configure > everything with key/value pairs. At least the driver I co-wrote works that > way. > > I would be nice to have a doc area where we write this kind of stuff down. > > Gary > > On Tue, Jul 26, 2016 at 10:33 AM, Ralph Goers <ralph.go...@dslextreme.com

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

:33 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > Has anybody asked for that? To be honest, the JNDI API is one of the worst > designs ever. It is impossible not to get an exception during normal > operation. If I was going to implement “advanced” configuration

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

ld be bits and pieces of > different components like this last request. > > Gary > > On Tue, Jul 26, 2016 at 9:02 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > To do what? I’ve never really used JNDI for much (except

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

To do what? I’ve never really used JNDI for much (except when I actually wanted to access LDAP). Ralph > On Jul 26, 2016, at 8:49 AM, Gary Gregory wrote: > > Any thoughts on a JNDI configuration epic? > > Gary > > -- Forwarded message -- > From:

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393943#comment-15393943 ] Ralph Goers commented on LOG4J2-1477: - Yeah, I got confused by https://blogs.oracle.com/java

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393134#comment-15393134 ] Ralph Goers commented on LOG4J2-1477: - I would suggest this issue be deferred until the minimum

[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=15392641#comment-15392641 ] Ralph Goers commented on LOG4J2-1465: - I agree with Gary. > Default layouts for various append

[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=15392204#comment-15392204 ] Ralph Goers commented on LOG4J2-1465: - IMO, changing default values should rarely be done

Re: Apache Spark now more Log4j 2 friendly

Cool, Thanks! Ralph > On Jul 25, 2016, at 1:08 AM, Mikael Ståldal wrote: > > I have helped Apache Spark to be a bit more Log4j 2 friendly: > > https://issues.apache.org/jira/browse/SPARK-16416 > > -- > > > Mikael Ståldal > Senior software developer > > Magine

[jira] [Commented] (LOG4J2-1313) not working

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391365#comment-15391365 ] Ralph Goers commented on LOG4J2-1313: - I doubt it. First, from what I can tell the PluginValue

[jira] [Commented] (LOG4J2-949) No MDC parameters in Syslog

[ https://issues.apache.org/jira/browse/LOG4J2-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390844#comment-15390844 ] Ralph Goers commented on LOG4J2-949: Actually Gary, they seem to be complaining that they don't see

[jira] [Commented] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390252#comment-15390252 ] Ralph Goers commented on LOG4J2-1467: - Your last sentence is key. The whole point of LoaderUtil

Re: Serializable Logger

re the justification was so that serializable classes can still > use a Logger instance field (not everyone uses a static field for the Logger > for some reason). > > On 21 July 2016 at 11:32, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com&g

Re: [1/4] logging-log4j2 git commit: Add AutoCloseableLock.

> give you that of course. > > The "l" lvar is what the Java syntax requires but there is no extra object > created by configLock.lock(), which returns "this". > > Gary > > > On Thu, Jul 21, 2016 at 3:12 PM, Matt Sicker <boa...@g

Re: [1/4] logging-log4j2 git commit: Add AutoCloseableLock.

course. > > The "l" lvar is what the Java syntax requires but there is no extra object > created by configLock.lock(), which returns "this". > > Gary > > > On Thu, Jul 21, 2016 at 3:12 PM, Matt Sicker <boa...@gmail.com > <mailto:boa...@

Re: [1/4] logging-log4j2 git commit: Add AutoCloseableLock.

} > ... > } > > Yes, AutoCloseableLock is an extra object on top of the Lock itself, I'll > give you that of course. > > The "l" lvar is what the Java syntax requires but there is no extra object > created by configLock.lock(), which returns

Re: [1/4] logging-log4j2 git commit: Add AutoCloseableLock.

object on top of the Lock itself, I'll > give you that of course. > > The "l" lvar is what the Java syntax requires but there is no extra object > created by configLock.lock(), which returns "this". > > Gary > > > On Thu, Jul 21, 2016 at 3:12

Re: [1/4] logging-log4j2 git commit: Add AutoCloseableLock.

Why is it that I recall just reading about why the JDK implementors decided that implementing an autocloseable lock was a bad idea? How is this really any different than doing synchronized(LOCK) { return MAP.containsKey(name); } so long as everything else is doing it similarly? From

Re: Lock pattern

What is a mismatch? Things that are all AutoCloseable all used to have an instance of the object created and then make sure it was closed during a finally call. Locks generally don’t work that way. They are typically created when they object they reside in is created and are destroyed when

Re: Serializable Logger

I asked myself the same question and I guess the answer is that Logger is included in lots of classes, many of which are Serializable. It would be easier for us to make AbstractLogger Serializable then for all the users to mark it as transient and have to manually instantiate the Logger during

Re: Release plan

Generally, the release number and release date dictate themselves. Since we use semantic versioning we only increase the second number when a non-insignificant feature is added (I didn’t use significant on purpose as some features aren’t really significant but they aren’t insignificant

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

Yeah, it is another case of the test not knowing when the gzip has finished. Ralph > On Jul 20, 2016, at 9:50 AM, Gary Gregory wrote: > > The failure: > >

Re:

AutoCloseable? I guess I wouldn’t think it would be all that common to use that, but OK. Most of the time I expect it will get used in some other initialize method and shutdown would be called in some sort of termination handler, much like the Servlet spec does. So unlike something like a

[jira] [Commented] (LOG4J2-1468) EJBs' Concurrent Initilization Phase Logs Issue

[ https://issues.apache.org/jira/browse/LOG4J2-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385869#comment-15385869 ] Ralph Goers commented on LOG4J2-1468: - Is this a duplicate or at least similar to LOG4J2-1094

[jira] [Comment Edited] (LOG4J2-1470) Add convenience API Configurator.initializeResource(String, ClassLoader, String)

[ https://issues.apache.org/jira/browse/LOG4J2-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385267#comment-15385267 ] Ralph Goers edited comment on LOG4J2-1470 at 7/20/16 3:42 AM: -- What

[jira] [Commented] (LOG4J2-1470) Add convenience API Configurator.initializeResource(String, ClassLoader, String)

[ https://issues.apache.org/jira/browse/LOG4J2-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385267#comment-15385267 ] Ralph Goers commented on LOG4J2-1470: - What is the difference between that and {code} final

[jira] [Commented] (LOG4J2-1469) I wish the json layout used a map structure for the context map instead of a list of map entry objects.

[ https://issues.apache.org/jira/browse/LOG4J2-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384975#comment-15384975 ] Ralph Goers commented on LOG4J2-1469: - What version of Log4j are you using? I believe

[jira] [Commented] (LOG4J2-1436) Log4j2 migration tools

[ https://issues.apache.org/jira/browse/LOG4J2-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383591#comment-15383591 ] Ralph Goers commented on LOG4J2-1436: - I would not be thrilled with this. At least by requiring

Re: Log4J 1.x and JDK 9

; >>>> And get ready for a GitHub fork... >> >>>> >> >>>> Gary >> >>>> >> >>>> On Thu, Jul 14, 2016 at 10:03 AM, Remko Popma <remko.po...@gmail.com >> >>>> <mailto:remko.po...@gmail.com>&g

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379955#comment-15379955 ] Ralph Goers commented on LOG4J2-1226: - I would love to change the default layout to something else

Re: Log4j should manage it's own threads

ou'll just want to have a good abstraction built so you can >> plug in the right implementation at runtime (non-container vs container). >> >> Cheers, >> Paul >> >> On Thu, Jul 14, 2016 at 4:34 PM, Ralph Goers <ralph.go...@dslextreme.com >> <mailt

Re: Log4j should manage it's own threads

in the right implementation at runtime (non-container vs container). > > Cheers, > Paul > > On Thu, Jul 14, 2016 at 4:34 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I’m not aware that frameworks like Log4j actua

Re: Log4j should manage it's own threads

I’m not aware that frameworks like Log4j actually adhere to those guidelines. It is too difficult to write code that works in both the JEE and non-JEE environments. Ralph > On Jul 14, 2016, at 1:07 PM, Paul Benedict wrote: > > In an EE environment, don't create your own

Re: Log4J 1.x and JDK 9

pport > users who did customizations to Log4j 1.2. > > On Fri, Jul 15, 2016 at 1:02 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > That would rule out building on a Mac. I’d have to try it from a Linux VM. > I think Gary m

Re: Log4J 1.x and JDK 9

> the right places. > > Gary > > On Jul 14, 2016 9:02 AM, "Ralph Goers" <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > That would rule out building on a Mac. I’d have to try it from a Linux VM. > I think Gary might have buil

Re: Log4J 1.x and JDK 9

That would rule out building on a Mac. I’d have to try it from a Linux VM. I think Gary might have built Log4j 1 in the past. Ralph > On Jul 14, 2016, at 8:52 AM, Paul Benedict wrote: > > Matt, I guess you need JDK 1.4.2 on your machine to have artifact >

Re: Log4J 1.x and JDK 9

I should also point out that I am aware that Log4j 2 has problems building against Java 9. We need to start tackling those ASAP. Ralph > On Jul 14, 2016, at 8:47 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > I am not sure how that “patch” integrates with Log4j but

Re: Log4J 1.x and JDK 9

I am not sure how that “patch” integrates with Log4j but I get the idea of the problem. To be honest, I have very mixed feelings about creating a patch release for this. Ralph > On Jul 14, 2016, at 7:56 AM, Paul Benedict wrote: > > According to this poster, it appears

[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=15371899#comment-15371899 ] Ralph Goers commented on LOG4J2-1457: - The patch looks fine to me. I don't think a separate method

[jira] [Commented] (LOG4J2-1059) log4j2 Configuration File not found in shaded jar

[ https://issues.apache.org/jira/browse/LOG4J2-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371423#comment-15371423 ] Ralph Goers commented on LOG4J2-1059: - We really should have a tool that does it. > log

[jira] [Comment Edited] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370656#comment-15370656 ] Ralph Goers edited comment on LOG4J2-1226 at 7/11/16 12:42 PM: --- 1. I

<    1   2   3   4   5   6   7   8   9   10   >