[jira] [Commented] (LOG4J2-1094) Multi thread initialization problem

[ https://issues.apache.org/jira/browse/LOG4J2-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259610#comment-15259610 ] Remko Popma commented on LOG4J2-1094: - Wouldn't it be better to block until the user-

[jira] [Closed] (LOG4J2-650) Cannot get named LoggerConfig from Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-650. -- Resolution: Fixed Closing due to lack of feedback from reporter. > Cannot get named LoggerConfig from C

[jira] [Commented] (LOG4J2-761) Move performance tests from JUnit to log4j-perf

[ https://issues.apache.org/jira/browse/LOG4J2-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259598#comment-15259598 ] Ralph Goers commented on LOG4J2-761: What is going on with this issue? Are you working

[jira] [Assigned] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly with Logj2 2.3 version jars

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1086: --- Assignee: Ralph Goers > SizeBasedTriggeringPolicy is not working properly with Logj2 2.3 ver

[jira] [Assigned] (LOG4J2-1143) Lookup Plugin not found

[ https://issues.apache.org/jira/browse/LOG4J2-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1143: --- Assignee: Ralph Goers > Lookup Plugin not found > --- > >

[jira] [Closed] (LOG4J2-565) Log4j2 loading time on single-board (embedded) computers

[ https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-565. -- Resolution: Fixed It seems the reporter lost interest. > Log4j2 loading time on single-board (embedded)

[jira] [Assigned] (LOG4J2-1332) Null/empty messages are not handled properly in RFC5424Layout

[ https://issues.apache.org/jira/browse/LOG4J2-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1332: --- Assignee: Ralph Goers > Null/empty messages are not handled properly in RFC5424Layout >

[jira] [Assigned] (LOG4J2-1243) Faulty placeholder substitution in config xml

[ https://issues.apache.org/jira/browse/LOG4J2-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1243: --- Assignee: Ralph Goers > Faulty placeholder substitution in config xml >

[jira] [Commented] (LOG4J2-1243) Faulty placeholder substitution in config xml

[ https://issues.apache.org/jira/browse/LOG4J2-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259590#comment-15259590 ] Ralph Goers commented on LOG4J2-1243: - If I am understanding this issue correctly the

[jira] [Assigned] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1359: --- Assignee: Ralph Goers > Add support for Java 9 StackWalker API in ReflectionUtil > -

[jira] [Commented] (LOG4J2-1094) Multi thread initialization problem

[ https://issues.apache.org/jira/browse/LOG4J2-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259589#comment-15259589 ] Ralph Goers commented on LOG4J2-1094: - SLF4J solves this problem by having "substitut

[jira] [Assigned] (LOG4J2-1094) Multi thread initialization problem

[ https://issues.apache.org/jira/browse/LOG4J2-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1094: --- Assignee: Ralph Goers > Multi thread initialization problem > --

[jira] [Commented] (LOG4J2-1095) How can we have multiple Configurations?

[ https://issues.apache.org/jira/browse/LOG4J2-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259577#comment-15259577 ] Ralph Goers commented on LOG4J2-1095: - Do we still need this issue? It would seem to

Jenkins build became unstable: Log4j 2.x #1913

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

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

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-673) plugin preloading fails in shaded jar files

[ https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259438#comment-15259438 ] ASF GitHub Bot commented on LOG4J2-673: --- Github user jvz commented on the pull reque

[jira] [Commented] (LOG4J2-813) MarkerManager Log4jMarker.hasParents() returns opposite of correct result

[ https://issues.apache.org/jira/browse/LOG4J2-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259437#comment-15259437 ] ASF GitHub Bot commented on LOG4J2-813: --- Github user asfgit closed the pull request

[jira] [Commented] (LOG4J2-1157) log4j2 exception covers real compiler error (PR on GitHub)

[ https://issues.apache.org/jira/browse/LOG4J2-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259436#comment-15259436 ] ASF GitHub Bot commented on LOG4J2-1157: Github user asfgit closed the pull reque

[jira] [Commented] (LOG4J2-673) plugin preloading fails in shaded jar files

[ https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259435#comment-15259435 ] ASF GitHub Bot commented on LOG4J2-673: --- Github user asfgit closed the pull request

Re: Performance page

Either in the manual or a link above it Sent from my iPhone > On Apr 26, 2016, at 4:41 PM, Remko Popma wrote: > > Will do. Was on my TODO-eventually list but I'll move it up. :-) > Shall we included it in the manual then? > >> On Wed, Apr 27, 2016 at 6:23 AM, Ralph Goers >> wrote: >> Remko,

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

This is our old friend bz2. Sent from my iPhone > On 2016/04/27, at 8:05, Apache Jenkins Server > wrote: > > See > > > - > To unsubscribe, e-mail: log4j-dev-unsubscr...@log

Re: CLIRR dependency

SME = Subject Matter Expert. Gary On Tue, Apr 26, 2016 at 3:42 PM, Matt Sicker wrote: > What's an SME? Also, now that you mention that, I think a release might > take a little bit longer to make sure 6.0 is actually ready for release. > The project sounds interesting, so I'll start looking at i

Re: Performance page

Will do. Was on my TODO-eventually list but I'll move it up. :-) Shall we included it in the manual then? On Wed, Apr 27, 2016 at 6:23 AM, Ralph Goers wrote: > Remko, > > The performance page hasn’t been updated in quite some time. It really > could use some of your nice graphs. Also, it isn’t

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

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

Re: CLIRR dependency

What's an SME? Also, now that you mention that, I think a release might take a little bit longer to make sure 6.0 is actually ready for release. The project sounds interesting, so I'll start looking at it more over the next few days. On 26 April 2016 at 16:55, Gary Gregory wrote: > I think there

Re: CLIRR dependency

I think there are two areas that may need work: Make sure Java 8 is supported. This might need a Jira scan for at leat one patch IIRC. Make sure the public API is set and good since this is the first release under the bcel6 package. We'd need an SME here... Gary On Apr 26, 2016 12:30 PM, "Gary G

Performance page

Remko, The performance page hasn’t been updated in quite some time. It really could use some of your nice graphs. Also, it isn’t linked from the main menu. The only way I know of to find it is by clicking a link embedded in the About page. Do you think you could enhance that page? It would

Re: CLIRR dependency

And 6.0 and 5.2 are not BC, diff packages and Maven coords, so Clirr would need an update. Gary On Tue, Apr 26, 2016 at 9:27 AM, Matt Sicker wrote: > Which version of BCEL does CLIRR need? BCEL trunk is versioned as > 6.0-SNAPSHOT, but the latest release was 5.2. > > On 26 April 2016 at 11:19,

Re: logging-log4j2 git commit: Add missing license headers

Keeping it all in one place was convenient for me during development. I will clean this up. On Wed, Apr 27, 2016 at 2:02 AM, Ralph Goers wrote: > You are welcome, but I am curious as to why the shell script and .bat file > are located in the middle of the java class hierarchy and not under > src

Re: Register Log4j 2 in Graylog marketplace

Probably various things from src/site/xdoc/ (not from manual/). On 26 April 2016 at 12:03, Ralph Goers wrote: > src/site/** ? What exactly are you wanting to generate a readme from? > Certainly not everything under src/site. > > Ralph > > > On Apr 26, 2016, at 2:27 AM, Mikael Ståldal > wrote: >

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

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

Re: Register Log4j 2 in Graylog marketplace

src/site/** ? What exactly are you wanting to generate a readme from? Certainly not everything under src/site. Ralph > On Apr 26, 2016, at 2:27 AM, Mikael Ståldal wrote: > > Would it be possible to generate README.md from src/site/** ? > > On Mon, Apr 25, 2016 at 6:55 PM, Matt Sicker

Re: logging-log4j2 git commit: Add missing license headers

You are welcome, but I am curious as to why the shell script and .bat file are located in the middle of the java class hierarchy and not under src/test/resources? Ralph > On Apr 26, 2016, at 9:06 AM, Remko Popma wrote: > > Thank you! > > On Wed, Apr 27, 2016 at 1:04 AM,

[jira] [Comment Edited] (LOG4J2-1295) Automated testing to verify no temporary objects allocated in gc-free configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258437#comment-15258437 ] Remko Popma edited comment on LOG4J2-1295 at 4/26/16 4:53 PM: -

[jira] [Commented] (LOG4J2-1295) Automated testing to verify no temporary objects allocated in gc-free configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258437#comment-15258437 ] Remko Popma commented on LOG4J2-1295: - Our tests randomly fail with this exception: {

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

I raised this issue: https://github.com/google/allocation-instrumenter/issues/15 Hopefully it is being maintained... On Wed, Apr 27, 2016 at 1:23 AM, Remko Popma wrote: > Yes, this looks like a bug in the Google AllocationRecorder >

Re: CLIRR dependency

Which version of BCEL does CLIRR need? BCEL trunk is versioned as 6.0-SNAPSHOT, but the latest release was 5.2. On 26 April 2016 at 11:19, Matt Sicker wrote: > I'll probably need all the permission updates. I can take a look at > starting the process either today or tomorrow. > > On 26 April 201

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

Yes, this looks like a bug in the Google AllocationRecorder : The NullPointerException we are seeing occurs when a shutdown hook allocates a new objec

Re: CLIRR dependency

I'll probably need all the permission updates. I can take a look at starting the process either today or tomorrow. On 26 April 2016 at 10:40, Gary Gregory wrote: > From my POV, the project needs minor POM updating to current versions of > plugins and 3rd party bits and then testing and then go.

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

Do you mean this? https://builds.apache.org/job/Log4j%202.x/1909/org.apache.logging.log4j$log4j-core/testReport/org.apache.logging.log4j.core/GcFreeMixedSyncAyncLoggingTest/testNoAllocationDuringSteadyStateLogging/ On 26 April 2016 at 10:29, Ralph Goers wrote: > Any idea how to determine what ca

Re: Register Log4j 2 in Graylog marketplace

I'm sure some sweet XSLT could do that. On 26 April 2016 at 04:27, Mikael Ståldal wrote: > Would it be possible to generate README.md from src/site/** ? > > On Mon, Apr 25, 2016 at 6:55 PM, Matt Sicker wrote: > >> I noticed that after I sent the first email ;) >> >> We can probably include info

Re: logging-log4j2 git commit: Add missing license headers

Thank you! On Wed, Apr 27, 2016 at 1:04 AM, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 6ddc0250c -> 73a678189 > > > Add missing license headers > > > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo > Commit: > http://git-wip-us.apache.org/re

Re: CLIRR dependency

>From my POV, the project needs minor POM updating to current versions of plugins and 3rd party bits and then testing and then go. I can take a look later today. More fixes can be done through RERO IMO. Thank you for RM'ing! Gary On Apr 26, 2016 8:23 AM, "Matt Sicker" wrote: > I mean if the c

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

Any idea how to determine what caused this to fail? Ralph > On Apr 26, 2016, at 8:07 AM, Apache Jenkins Server > wrote: > > See > > > - > To unsubscribe, e-mail: log4j

Re: [jira] [Closed] (LOG4J2-1357) GelfLayout should have option to not log stacktraces for logged Throwables

I see a specific need in GelfLayout since a stacktrace can be quite large, and you might want to avoid large GELF messages since they are sometimes sent as UDP packages. PatternLayout and RFC5425Layout already supports this (in a slightly different way). CsvLayout and SyslogLayout never include s

Re: CLIRR dependency

I mean if the code is ready, I could step up and handle that. On 25 April 2016 at 20:26, Gary Gregory wrote: > Volunteers... > On Apr 25, 2016 6:18 PM, "Matt Sicker" wrote: > >> What's preventing a Commons BCEL release? >> >> On 25 April 2016 at 19:41, Ralph Goers >> wrote: >> >>> Gary updated

Jenkins build became unstable: Log4j 2.x #1909

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

Fwd: [jira] [Closed] (LOG4J2-1357) GelfLayout should have option to not log stacktraces for logged Throwables

Should all layouts support this? How about at higher levels like the Config? Gary -- Forwarded message -- From: "Mikael Ståldal (JIRA)" Date: Apr 26, 2016 5:43 AM Subject: [jira] [Closed] (LOG4J2-1357) GelfLayout should have option to not log stacktraces for logged Throwables To:

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

[ https://issues.apache.org/jira/browse/LOG4J2-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-494. Resolution: Fixed Fix Version/s: 2.6 The enhancement has been merged to master. Thanks for th

[jira] [Closed] (LOG4J2-1357) GelfLayout should have option to not log stacktraces for logged Throwables

[ https://issues.apache.org/jira/browse/LOG4J2-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1357. -- > GelfLayout should have option to not log stacktraces for logged Throwables >

[jira] [Resolved] (LOG4J2-1357) GelfLayout should have option to not log stacktraces for logged Throwables

[ https://issues.apache.org/jira/browse/LOG4J2-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1357. Resolution: Fixed Fixed in master. > GelfLayout should have option to not log stacktraces

[jira] [Updated] (LOG4J2-1357) GelfLayout should have option to not log stacktraces for logged Throwables

[ https://issues.apache.org/jira/browse/LOG4J2-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1357: --- Fix Version/s: 2.6 > GelfLayout should have option to not log stacktraces for logged Throwabl

Re: Register Log4j 2 in Graylog marketplace

Would it be possible to generate README.md from src/site/** ? On Mon, Apr 25, 2016 at 6:55 PM, Matt Sicker wrote: > I noticed that after I sent the first email ;) > > We can probably include info from the wiki, FAQ, or some other site manual > pages. > > On 25 April 2016 at 11:12, Mikael Ståldal