[jira] [Commented] (LOG4J2-494) Support composite configurations

[ https://issues.apache.org/jira/browse/LOG4J2-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15116311#comment-15116311 ] Ralph Goers commented on LOG4J2-494: FWIW, I never had any intention of supporting includes as part

Re: logging-log4j2 git commit: LOG4J2-124 - Add shutdown methods to LogManager

al word to boot. > > On 25 January 2016 at 18:15, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Yes, well - Serializable actually sounds like it should be a real word. > Shutdownable doesn’t - in fact, my mail editor just split

[jira] [Commented] (LOG4J2-494) Support composite configurations

[ https://issues.apache.org/jira/browse/LOG4J2-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15116312#comment-15116312 ] Ralph Goers commented on LOG4J2-494: I would suggest that if you want to add support for import

Re: logging-log4j2 git commit: LOG4J2-124 - Add shutdown methods to LogManager

terface is "capable" of > that functionality. IOW we have Serializable vs. SerializationCabable, which > means the same thing. > > Gary > > On Mon, Jan 25, 2016 at 7:27 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>

Re: logging-log4j2 git commit: LOG4J2-124 - Add shutdown methods to LogManager

s name to the fact that the Capable > postfix is redundant since a class implementing any interface is "capable" of > that functionality. IOW we have Serializable vs. SerializationCabable, which > means the same thing. > > Gary > > On Mon, Jan 25, 201

Re: logging-log4j2 git commit: LOG4J2-124 - Add shutdown methods to LogManager

tContext(some > params)). > > I would be in favor of removing these three convenience methods: > * shutdown(String, boolean) > * shutdown(String, ClassLoader, boolean) > * shutdown(ClassLoader, boolean) > > Thoughts? -Remko > > > On Mon, Jan 25, 2016

[jira] [Resolved] (LOG4J2-124) Gracefully stopping LogContext using the api interfaces

[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-124. Resolution: Fixed Fix has been applied to master. Please verify and close. > Gracefully stopp

Re: logging-log4j2 git commit: LOG4J2-124 - Add shutdown methods to LogManager

t; Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/2df3f0e7 > <http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/2df3f0e7> > Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/2df3f0e7 > <http://git-wip-us.apache.org/repos/asf/logging-l

Re: logging-log4j2 git commit: LOG4J2-124 - Add shutdown methods to LogManager

() > org.apache.logging.log4j.LogManager.shutdown(boolean) > org.apache.logging.log4j.LogManager.shutdown(ClassLoader, boolean) > > have no senders, so no unit tests? > > Gary > > > > > On Mon, Jan 25, 2016 at 6:54 AM, Ralph Goers <ralph.go...@dslextreme.com

[jira] [Comment Edited] (LOG4J2-1222) Initializing Logger during JVM shutdown fails with FATAL error

[ https://issues.apache.org/jira/browse/LOG4J2-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114219#comment-15114219 ] Ralph Goers edited comment on LOG4J2-1222 at 1/24/16 6:51 AM: -- Rats. No. I

Re: [2/5] logging-log4j2 git commit: Verify that file sizes are parsed correctly.

ng-log4j2/diff/c1b8cb85 > <http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/c1b8cb85> > > Branch: refs/heads/LOG4J-1181 > Commit: c1b8cb85ca0a5fdde491c02d636b7e7813222b9b > Parents: 419a7b2 > Author: Ralph Goers <rgo...@apache.org <mailto:rgo...@apache.org>&g

[jira] [Commented] (LOG4J2-1222) Initializing Logger during JVM shutdown fails with FATAL error

[ https://issues.apache.org/jira/browse/LOG4J2-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114219#comment-15114219 ] Ralph Goers commented on LOG4J2-1222: - Rats. No. I didn't even realize I hadn't switched back

[jira] [Resolved] (LOG4J2-1222) Initializing Logger during JVM shutdown fails with FATAL error

[ https://issues.apache.org/jira/browse/LOG4J2-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1222. - Resolution: Fixed Fix Version/s: 2.5.1 During shutdown trying to create a LoggerContext

Re: Log4j 2.6 vs. 2.5.1

stead. > > Ralph, do you feel like doing a 2.5.1 release? > > On Fri, Jan 22, 2016 at 3:41 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > IMO, every one of those should be type=“update”, not type=“add”, as they are > basi

[jira] [Commented] (LOG4J2-1222) Initializing Logger during JVM shutdown fails with FATAL error

[ https://issues.apache.org/jira/browse/LOG4J2-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114234#comment-15114234 ] Ralph Goers commented on LOG4J2-1222: - Yes. I just did that with SourceTree. It is in master now

Re: Log4j 2.6 vs. 2.5.1

IMO, every one of those should be type=“update”, not type=“add”, as they are basically all tweaks to existing stuff. That said, when I modify Logger to add more entry and exit methods that would justify 2.6. Ralph > On Jan 21, 2016, at 11:05 AM, Gary Gregory wrote: >

ApacheCon US 2016

Is anyone planning on going to ApacheCon this year. My employer has given me permission to go. The call for papers is still open so I am considering proposing something for Log4j. If I do would it be possible to “borrow” some stuff from any of you? I believe a few of you have done presentations

[jira] [Commented] (LOG4J2-1256) strange classloader failure

[ https://issues.apache.org/jira/browse/LOG4J2-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104995#comment-15104995 ] Ralph Goers commented on LOG4J2-1256: - Can you try just using the ThrowableConverter instead

Re: Rfc5424Layout.eventPrefix

You asked this exact question on September 27, 2013. I doubt you got an answer. The usage of the eventPrefix was removed in the patch for LOG4J2-355 and was noticed by the author of the patch. Unfortunately I was in the middle of looking for a job at the time and don’t seem to have responded.

[jira] [Commented] (LOG4J2-1256) strange classloader failure

[ https://issues.apache.org/jira/browse/LOG4J2-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103482#comment-15103482 ] Ralph Goers commented on LOG4J2-1256: - Are you getting log4j from the log4j-core jar or did you

[jira] [Commented] (LOG4J2-1256) strange classloader failure

[ https://issues.apache.org/jira/browse/LOG4J2-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103595#comment-15103595 ] Ralph Goers commented on LOG4J2-1256: - I don't see how not being Serializable would matter at all. I

[jira] [Created] (LOG4J2-1255) Logger.entry and Logger.exit should support Messages.

Ralph Goers created LOG4J2-1255: --- Summary: Logger.entry and Logger.exit should support Messages. Key: LOG4J2-1255 URL: https://issues.apache.org/jira/browse/LOG4J2-1255 Project: Log4j 2 Issue

[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=15101929#comment-15101929 ] Ralph Goers commented on LOG4J2-658: Using a timer makes it likely that it would be hit or miss

[jira] [Commented] (LOG4J2-1255) Logger.entry and Logger.exit should support Messages.

[ https://issues.apache.org/jira/browse/LOG4J2-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102442#comment-15102442 ] Ralph Goers commented on LOG4J2-1255: - Thanks Gary. I will see if I can't accommodate your needs

Re: Log4j for Scala

l.stal...@magine.com> wrote: > > It is unfortunate that we need two almost identical projects, but I don't > know any other solution when using Maven. > > What I want is a binary release. > >> On Wed, Jan 13, 2016 at 5:30 AM, Ralph Goers <ralph.go...@dslextreme.com> &

Re: [jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

Then why do you need a patch for 2.2? Ralph > On Jan 13, 2016, at 8:55 PM, sampath kumar <sampath...@gmail.com> wrote: > > We are using Java 8 > > Regards, > Sampath Kumar > Sent from Mymobile > > On Jan 13, 2016 10:33 PM, "Ralph Goers" <

[jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096496#comment-15096496 ] Ralph Goers commented on LOG4J2-1221: - Michael, if there are other issues you would like to submit

Re: [jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

ampath...@gmail.com> wrote: > > Can this patch back ported log4j 2.2 ? > > Regards, > Sampath Kumar > > On Jan 13, 2016 10:08 PM, "Ralph Goers (JIRA)" <j...@apache.org > <mailto:j...@apache.org>> wrote: > >

Re: Log4j for Scala

this will get added to the complete Log4j distribution so creating a project to build one for scala seems like overkill. Ralph > On Jan 12, 2016, at 9:59 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > OK - I suppose it would be OK to release from the branch. I will try to

Re: Log4j for Scala

two 2.5.1’s, even if one has a classifier, is going to lead to confusion. Ralph > On Jan 12, 2016, at 10:05 AM, Mikael Ståldal <mikael.stal...@magine.com> > wrote: > > That branch is up-to-date with master, and builds properly. > > On Tue, Jan 12, 2016 at 5:59 P

Re: Log4j for Scala

Oh - And that probably means that you probably should add the scala stuff to a fork of the 2.5 release so that it can refer to artifacts that have been released already. Ralph > On Jan 12, 2016, at 11:21 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > OK - but I don’t

Re: Log4j for Scala

That is what I am talking about. It seems strange to have a log4j 2 component at 2.5.1-alpha1. Ralph > On Jan 12, 2016, at 11:50 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > How about 2.5.1-alpha1? > > Gary > > On Tue, Jan 12, 2016 at 10:2

Re: List vs. Set

..@gmail.com>>> wrote: > > List getPluginPackages(); > > > > G > > > > On Mon, Jan 11, 2016 at 8:12 PM, Paul Benedict > > <<mailto:pbened...@apache.org > > <mailto:pbened...@apache.org>>pbened...@apache.org > > <mailto:pbened...

Re: Log4j for Scala

OK - I suppose it would be OK to release from the branch. I will try to take a look at it this evening and make suggestions. Ralph > On Jan 12, 2016, at 9:49 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote: > > In branch LOG4J-1181 > > On Tue, Jan 12, 2016 at

Re: JSONLayout serializes the MDC as a List<Map<String,String>>?

If there is a flag that causes the new structure to be generated then he would get the performance gain when it is enabled. The current structure would be generated when the flag is not set. Ralph > On Jan 12, 2016, at 9:14 AM, Mikael Ståldal wrote: > > But I guess

Re: Log4j for Scala

e we on this? > > On Mon, Dec 14, 2015 at 6:21 PM, Mikael Ståldal <mikael.stal...@magine.com > <mailto:mikael.stal...@magine.com>> wrote: > Sounds good then. > > On Mon, Dec 14, 2015 at 6:13 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@d

Re: List vs. Set

It is returning a List already. Does it really matter much? Ralph > On Jan 11, 2016, at 6:04 PM, Gary Gregory wrote: > > Should APIs like: > > org.apache.logging.log4j.core.config.Configuration.getPluginPackages() > > really return a List instead of a Set? > > Gary

Re: log4j2 FlumeAppender

Choosing which one to use is purely based on your needs. The remote client operates synchronously and does not store the event on disk. The other two are asynchronous and guarantee delivery by storing to disk. The embedded agent embeds a Flume agent with a file channel. This is extremely

Re: Git status update

So we need to update the wiki page. Ralph > On Jan 10, 2016, at 11:59 AM, Gary Gregory wrote: > > FYI, a new release req. > > Gary > -- Forwarded message -- > From: David Nalley > > Date: Sun, Jan 10, 2016 at

[jira] [Commented] (LOG4J2-603) Use Gora as storage abstraction for Log4j 2.X

[ https://issues.apache.org/jira/browse/LOG4J2-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091240#comment-15091240 ] Ralph Goers commented on LOG4J2-603: If you have the source then you already have the web site source

[jira] [Commented] (LOG4J2-1247) Can not build Log4j from git master due to a test failure in Log4j Core

[ https://issues.apache.org/jira/browse/LOG4J2-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090728#comment-15090728 ] Ralph Goers commented on LOG4J2-1247: - I ran the build on my Mac with success and then ran it in my

Re: Questions on submitting changes to the Log4j2 code base

FWIW, I have plans to create a log4j-audit subproject that could be used to implement what you have described, although it will be done differently than what you have done and won’t need any extensions to Log4j 2. I implemented a framework similar to what I have in mind at one of my former

Re: GitHub out of sync or did we miss a step in the release?

I missed creating a 2.5 tag from the 2.5-rc1 tag. 2.5-rc1 is the actual release. In the past I created the tag as 2.5 and then deleted it if the release failed. We aren’t allowed to do that any more. Ralph > On Jan 8, 2016, at 1:15 PM, Gary Gregory wrote: > > Hi All:

Re: POM errors in m2e

I am guessing it is because the parent pom also has the bundle plugin defined configured for the process-classes phase and in the log4j-1.2-api pom.xml no phase is specified so one doesn’t override the other. Ralph > On Jan 4, 2016, at 11:33 AM, Gary Gregory wrote: >

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

RollingAppenderSizeTest.testAppender:115 Error creating intput stream from target/rolling1/test1-01-04-2016-7.log.bz2: Could not create CompressorInputStream. This has been happening for quite a while now. Ralph > On Jan 4, 2016, at 5:46 PM, Gary Gregory wrote: > >

[jira] [Commented] (LOG4J2-1230) Concatenated SYSLOG Messages

[ https://issues.apache.org/jira/browse/LOG4J2-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082494#comment-15082494 ] Ralph Goers commented on LOG4J2-1230: - That is what I had in mind. > Concatenated SYSLOG Messa

[jira] [Commented] (LOG4J2-1241) Have a method that checks if logger debug is enabled and then does the logging

[ https://issues.apache.org/jira/browse/LOG4J2-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076522#comment-15076522 ] Ralph Goers commented on LOG4J2-1241: - logger.error, etc. already do this. > Have a met

[jira] [Resolved] (LOG4J2-1241) Have a method that checks if logger debug is enabled and then does the logging

[ https://issues.apache.org/jira/browse/LOG4J2-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1241. - Resolution: Not A Problem > Have a method that checks if logger debug is enabled and then d

[jira] [Comment Edited] (LOG4J2-1241) Have a method that checks if logger debug is enabled and then does the logging

[ https://issues.apache.org/jira/browse/LOG4J2-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076522#comment-15076522 ] Ralph Goers edited comment on LOG4J2-1241 at 1/2/16 1:51 PM: - logger.error

[jira] [Commented] (LOG4J2-908) JSONLayout doesn't add a comma between log events

[ https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076182#comment-15076182 ] Ralph Goers commented on LOG4J2-908: I think I am very confused. This issue implies

[jira] [Commented] (LOG4J2-1237) Header should be on its own line

[ https://issues.apache.org/jira/browse/LOG4J2-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15075356#comment-15075356 ] Ralph Goers commented on LOG4J2-1237: - What about \n? > Header should be on its own l

[jira] [Commented] (LOG4J2-1237) Header should be on its own line

[ https://issues.apache.org/jira/browse/LOG4J2-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15075316#comment-15075316 ] Ralph Goers commented on LOG4J2-1237: - Can you include a newline in your header? > Header sho

[jira] [Commented] (LOG4J2-1231) Log files are under lock, not able to view them until JVM stop.

[ https://issues.apache.org/jira/browse/LOG4J2-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074056#comment-15074056 ] Ralph Goers commented on LOG4J2-1231: - Yes, in which case it isn't a Log4j problem. > Log fi

Re: Jenkins build became unstable: Log4j 2.x #1608

Jenkins appears to be invoking maven to allow failed unit tests not to fail the build. If you look through each of the module summaries you will probably find a failure. Ralph > On Dec 29, 2015, at 7:12 PM, Gary Gregory wrote: > > Hm, how can the build be unstable

[jira] [Commented] (LOG4J2-1231) Log files are under lock, not able to view them until JVM stop.

[ https://issues.apache.org/jira/browse/LOG4J2-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073933#comment-15073933 ] Ralph Goers commented on LOG4J2-1231: - I ran your test application in my Windows 7 VM and had

[jira] [Comment Edited] (LOG4J2-913) Allow to load log4j2 configuration from a centralized repository, like a database or a webservice

[ https://issues.apache.org/jira/browse/LOG4J2-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073425#comment-15073425 ] Ralph Goers edited comment on LOG4J2-913 at 12/29/15 3:30 AM: -- That section

[jira] [Commented] (LOG4J2-913) Allow to load log4j2 configuration from a centralized repository, like a database or a webservice

[ https://issues.apache.org/jira/browse/LOG4J2-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073425#comment-15073425 ] Ralph Goers commented on LOG4J2-913: That section is what inspired LOG4J2-494, although the mechanism

Re: Bug report for Log4j [2015/12/27]

I don't think we want to retire bugzilla, although I do wish it was read only. I'll see about stopping the report. I have never looked at it. Ralph > On Dec 27, 2015, at 1:48 AM, Remko Popma wrote: > > Is it possible to retire this bugzilla? > > Sent from my iPhone >

Re: Bug report for Log4j [2015/12/27]

I have been told that bugzilla is now read-only for log4j 1 and the emails should stop. If we ever want new bugs for Log4j 1 I would suggest using Jira anyway. Ralph > On Dec 27, 2015, at 6:54 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > I don't think we want to

[jira] [Assigned] (LOG4J2-1222) Initializing Logger during JVM shutdown fails with FATAL error

[ https://issues.apache.org/jira/browse/LOG4J2-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1222: --- Assignee: Ralph Goers > Initializing Logger during JVM shutdown fails with FATAL er

[jira] [Commented] (LOG4J2-1231) Log files are under lock, not able to view them until JVM stop.

[ https://issues.apache.org/jira/browse/LOG4J2-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071933#comment-15071933 ] Ralph Goers commented on LOG4J2-1231: - Can you provide a small project that we can use to test

[jira] [Updated] (LOG4J2-1231) Log files are under lock, not able to view them until JVM stop.

[ https://issues.apache.org/jira/browse/LOG4J2-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1231: Description: Hi Team, The problem is when I use file appender with below configuration. In each

[jira] [Comment Edited] (LOG4J2-1230) Concatenated SYSLOG Messages

[ https://issues.apache.org/jira/browse/LOG4J2-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068766#comment-15068766 ] Ralph Goers edited comment on LOG4J2-1230 at 12/22/15 9:38 PM: --- The read

[jira] [Commented] (LOG4J2-1230) Concatenated SYSLOG Messages

[ https://issues.apache.org/jira/browse/LOG4J2-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068766#comment-15068766 ] Ralph Goers commented on LOG4J2-1230: - The read lock accomplishes nothing. There used to be a write

[jira] [Commented] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068344#comment-15068344 ] Ralph Goers commented on LOG4J2-1229: - The error shown in the stack trace occurs

[jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065537#comment-15065537 ] Ralph Goers commented on LOG4J2-1221: - If you want synchronous behavior don't use asynchronous

Re: Log4j for Scala

t include something in the version which marks it as preview. Such > as "2.5-beta1" > > On Sat, Dec 12, 2015 at 12:15 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I believe I could run the release plugin against just

Re: Log4j for Scala

Sure. Ralph > On Dec 14, 2015, at 9:41 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote: > > Can it still depend on log4-api version 2.5 then? > > > On Mon, Dec 14, 2015 at 5:37 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslex

[jira] [Closed] (LOG4J2-1223) I want set current date to "Active output target" in RollingFile.

[ https://issues.apache.org/jira/browse/LOG4J2-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1223. --- > I want set current date to "Active output target" i

[jira] [Resolved] (LOG4J2-1223) I want set current date to "Active output target" in RollingFile.

[ https://issues.apache.org/jira/browse/LOG4J2-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1223. - Resolution: Duplicate Closing as a duplicate. > I want set current date to "Activ

Re: Log4j for Scala

om my iPhone > >> On 2015/12/12, at 14:56, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> >> If it builds by default it will be part of the next release, which I am not >> certain is assured yet. I think that is why he wants to release it >> se

[jira] [Commented] (LOG4J2-1222) Initializing Logger during JVM shutdown fails with FATAL error

[ https://issues.apache.org/jira/browse/LOG4J2-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054525#comment-15054525 ] Ralph Goers commented on LOG4J2-1222: - I'm not sure why this wouldn't have happened in 2.3. Adding

[jira] [Commented] (LOG4J2-1222) Initializing Logger during JVM shutdown fails with FATAL error

[ https://issues.apache.org/jira/browse/LOG4J2-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054581#comment-15054581 ] Ralph Goers commented on LOG4J2-1222: - A unit test that we can use to verify the fix would be great

[jira] [Commented] (LOG4J2-1220) Thread context value is different for same thread.

[ https://issues.apache.org/jira/browse/LOG4J2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052783#comment-15052783 ] Ralph Goers commented on LOG4J2-1220: - If I had to guess I would suppose that the session id from

[jira] [Comment Edited] (LOG4J2-1220) Thread context value is different for same thread.

[ https://issues.apache.org/jira/browse/LOG4J2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052783#comment-15052783 ] Ralph Goers edited comment on LOG4J2-1220 at 12/11/15 1:52 PM: --- If I had

Re: Log4j for Scala

aster and _document_ it as "experimental, feedback > requested". > > That way we simply use our existing release process and instead of 2.5.1, our > next release would be 2.6. > > Sent from my iPhone > > On 2015/12/12, at 3:05, Ralph Goers <ralph.go...@dsl

Re: Log4j for Scala

, the artifact name could be log4j-scala-experimental. Ralph > On Dec 11, 2015, at 5:28 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > Should the package name include ".experimental." ? > > Gary > > On Fri, Dec 11, 2015 at 3:52 PM, Ralph Goers <ralph.

Re: Log4j for Scala

some use cases on the dev branch, so it > should be okay to build this module by default. No need for setting up a > separate profile AFAIC. > > Sent from my iPhone > > On 2015/12/12, at 9:43, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextrem

Re: Log4j for Scala

preview now when 2.5 is out? > > On Mon, Dec 7, 2015 at 3:58 AM, Gary Gregory <garydgreg...@gmail.com > <mailto:garydgreg...@gmail.com>> wrote: > On Dec 5, 2015 6:05 AM, "Ralph Goers" <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wr

[jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15053116#comment-15053116 ] Ralph Goers commented on LOG4J2-1221: - Looking at the issue you raised with the disruptor team

[jira] [Comment Edited] (LOG4J2-1220) Thread context value is different for same thread.

[ https://issues.apache.org/jira/browse/LOG4J2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052783#comment-15052783 ] Ralph Goers edited comment on LOG4J2-1220 at 12/11/15 1:52 PM: --- If I had

Re: Any interest in a fat jar?

te: > To the point of conveniences, the convenience is GREAT when I use cxf-bundle, > hamcrest-all, activemq-all, jetty-all, mockito-all, and so on, instead of > being forced to list out 50 or who-knows-how-many modules. For our big app > server, I just use bundles and be done with it unles

Re: Any interest in a fat jar?

My understanding is that most of the people who combine jars like this also include the classes from their application. For that reason I don’t think it would be helpful. Beyond that, I am not sure combining them makes it “super-convenient”. The only place this might be helpful is in OSGi, and

Re: Remko's schedule

giving a heads-up. >> >> Sounds super fun and interesting. What are you building this on? Any FOSS in >> there ;-) >> >> Gary >> >>> >>>> On Mon, Nov 30, 2015 at 10:30 PM, Ralph Goers <ralph.go...@dslextreme.com> >>>>

[jira] [Commented] (LOG4J2-1215) Documentation/XSD inconsistencies

[ https://issues.apache.org/jira/browse/LOG4J2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046999#comment-15046999 ] Ralph Goers commented on LOG4J2-1215: - Thanks! Yes, we have been a bit lax in keeping the xsd up

[jira] [Commented] (LOG4J2-1215) Documentation/XSD inconsistencies

[ https://issues.apache.org/jira/browse/LOG4J2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047088#comment-15047088 ] Ralph Goers commented on LOG4J2-1215: - If it was common I suspect we would have gotten more

Re: Jenkins build became unstable: Log4j 2.x #1593

This test has been failing for a while. I added a bit of logic to print the actual error since it was possible it could be something else. The old failure wasn’t printing the caused by… I suspect this means the file is empty or didn’t compress properly. Ralph > On Dec 8, 2015, at 2:41 PM,

Re: Jenkins build became unstable: Log4j 2.x #1593

No, never. If it did I would debug it. It only seems to fail on Jenkins periodically. Ralph > On Dec 8, 2015, at 6:36 PM, Remko Popma <remko.po...@gmail.com> wrote: > > Does this consistently fail on your machine? > > Sent from my iPhone > > On 2015/12/09, at

[VOTE] Log4j 2.5 rc1

This is a vote to release Log4j 2.5, the next version of the Log4j 2 project. Please download, test, and cast your votes on the log4j developers list. [] +1, release the artifacts [] -1, don't release because... The vote will remain open for 72 hours (or more if required). All votes are welcome

[jira] [Commented] (LOG4J2-1080) Drop events when the RingBuffer is full

[ https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044275#comment-15044275 ] Ralph Goers commented on LOG4J2-1080: - I just created the 2.5 release candidate so it is unlikely

[jira] [Comment Edited] (LOG4J2-1080) Drop events when the RingBuffer is full

[ https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044275#comment-15044275 ] Ralph Goers edited comment on LOG4J2-1080 at 12/7/15 2:31 AM: -- I just

Re: Log4j for Scala

gt;> How should we proceed on this? It would be good to be able to release some >> beta or preview version of this and get some feedback from Scala developers >> before we make the API final. >> >>> On Fri, Oct 30, 2015 at 1:10 AM, Ralph Goers <ralph.go...@dslext

Re: What do we do now to upload the maven site with the new home.apache.org change?

>> >> That sounds best. You should probably be the one to request it being the >> chair and all. ;) >> >> On 27 November 2015 at 02:32, Ralph Goers <ralph.go...@dslextreme.com >> <mailto:ralph.go...@dslextreme.com>> wrote: >> The only way I am awa

[jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038037#comment-15038037 ] Ralph Goers commented on LOG4J2-435: While it is true that Script, ScriptFile or ScriptRef could

[jira] [Comment Edited] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038015#comment-15038015 ] Ralph Goers edited comment on LOG4J2-435 at 12/3/15 4:17 PM: - The only

[jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038015#comment-15038015 ] Ralph Goers commented on LOG4J2-435: The only difference with what we are doing in general is that you

[jira] [Comment Edited] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038015#comment-15038015 ] Ralph Goers edited comment on LOG4J2-435 at 12/3/15 4:18 PM: - The only

[jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038714#comment-15038714 ] Ralph Goers commented on LOG4J2-435: Which means we already support it. > Feature request: a

[jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038721#comment-15038721 ] Ralph Goers commented on LOG4J2-435: If we did that then scriptcondition would have to support

[jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038263#comment-15038263 ] Ralph Goers commented on LOG4J2-435: That is JSR 223. That is what the Script and ScriptFile elements

<    7   8   9   10   11   12   13   14   15   16   >