Re: @Required on layout on AbstractAppender

I cannot see any real consequences yet, but in catalina.out I find: 2016-09-13 09:08:24,616 localhost-startStop-9 ERROR appender has no parameter that matches element policies 2016-09-13 09:08:24,618 localhost-startStop-9 ERROR appender has no parameter that matches element policies Re

Re: @Required on layout on AbstractAppender

What is the configuration that generates this error? Sent from my iPhone > On 2016/09/13, at 16:10, Steffen Offermann > wrote: > > I cannot see any real consequences yet, but in catalina.out I find: > >2016-09-13 09:08:24,616 localhost-startStop-9 ERROR appender has no > parameter that m

[jira] [Commented] (LOG4J2-1577) Add a Builder to the RoutingAppender and deprecate factory method

[ https://issues.apache.org/jira/browse/LOG4J2-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486620#comment-15486620 ] Gary Gregory commented on LOG4J2-1577: -- That's bogus, fixing... > Add a Builder to

Re: @Required on layout on AbstractAppender

This is the log4j2 configuration for the respective WAR (note that we use custom log levels): { "configuration" : { "status" : "warn", "name" : "OID", "packages" : "com.aixigo.tec.logging", "appenders" : { "appender" : [ { "type" : "

Re: @Required on layout on AbstractAppender

I guess I have an idea what might cause the error messages: We use a custom Logger implementation (to provide factory methods for our custom log levels). The current master version of Log4j2 may not be compatible with the generated Logger any more, so it has to be regenerated. I'll have to talk

Jenkins build became unstable: Log4j 2.x #2302

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

Re: @Required on layout on AbstractAppender

Nope, recreation of the custom Logger did not solve the problem. On 09/13/2016 10:56 AM, Steffen Offermann wrote: I guess I have an idea what might cause the error messages: We use a custom Logger implementation (to provide factory methods for our custom log levels). The current master version

Re: @Required on layout on AbstractAppender

It looks like this has already happened with Log4j2 v2.6.2, too. On 09/13/2016 11:13 AM, Steffen Offermann wrote: Nope, recreation of the custom Logger did not solve the problem. On 09/13/2016 10:56 AM, Steffen Offermann wrote: I guess I have an idea what might cause the error messages: We use

[jira] [Commented] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486772#comment-15486772 ] Gary Gregory commented on LOG4J2-1578: -- That was easier than I thought; I have a fir

[jira] [Commented] (LOG4J2-1577) Add a Builder to the RoutingAppender and deprecate factory method

[ https://issues.apache.org/jira/browse/LOG4J2-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486774#comment-15486774 ] Gary Gregory commented on LOG4J2-1577: -- Commit 363bc187d96dbd67ae0e2db39637e46d3f1d9

[jira] [Created] (LOG4J2-1579) jansi color not correct in tomcat console

TimAndy created LOG4J2-1579: --- Summary: jansi color not correct in tomcat console Key: LOG4J2-1579 URL: https://issues.apache.org/jira/browse/LOG4J2-1579 Project: Log4j 2 Issue Type: Question

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

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

[jira] [Created] (LOG4J2-1580) Log4j2 hangs when logging Unicode characters on appender with buffer size 1

Frederico Ferro Schuh created LOG4J2-1580: - Summary: Log4j2 hangs when logging Unicode characters on appender with buffer size 1 Key: LOG4J2-1580 URL: https://issues.apache.org/jira/browse/LOG4J2-1580

[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487022#comment-15487022 ] Pierrick HYMBERT commented on LOG4J2-1320: -- Hi [~garydgregory], sorry to insist

[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&focusedCommentId=15487137#comment-15487137 ] Remko Popma commented on LOG4J2-1447: - TODO add test {code} // log4j-api\src\test\ja

[jira] [Reopened] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1320: - Reopened because there seems to be some remaining work. > Custom plugins are not loaded, URL proto

Re: @Required on layout on AbstractAppender

Looking at the configuration, you have a RandomAccessFile appender (not a RollingRandomAccessFile appender) that you are trying to set a rollover policy on. Changing the appender type should fix it. Remko Sent from my iPhone > On 2016/09/13, at 18:24, Steffen Offermann > wrote: > > It lo

Re: @Required on layout on AbstractAppender

Thanks, Remko! Sounds reasonable. ;) On 09/13/2016 03:40 PM, Remko Popma wrote: Looking at the configuration, you have a RandomAccessFile appender (not a RollingRandomAccessFile appender) that you are trying to set a rollover policy on. Changing the appender type should fix it. Remko Sent f

[jira] [Comment Edited] (LOG4J2-1313) not working

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487278#comment-15487278 ] Leon Finker edited comment on LOG4J2-1313 at 9/13/16 1:54 PM: -

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

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487278#comment-15487278 ] Leon Finker commented on LOG4J2-1313: - Thank you Remko! The issue I reported is fixed

[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&focusedCommentId=15487469#comment-15487469 ] Remko Popma commented on LOG4J2-1447: - Fixed in master. > Garbage-free data structur

[jira] [Updated] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1576: Description: I have trouble running Clirr on a machine that only has Java 8 (ran into the "Invalid

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487521#comment-15487521 ] Remko Popma commented on LOG4J2-1576: - Basic features: http://revapi.org/modules/reva

[jira] [Commented] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487532#comment-15487532 ] Remko Popma commented on LOG4J2-1576: - I will go through the 150 reported breakages a

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

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

[jira] [Resolved] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1320. -- Resolution: Fixed The patch from August 29 (https://issues.apache.org/jira/secure/attachment/1

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

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

[jira] [Created] (LOG4J2-1581) Warning should not display stacktrace

Remko Popma created LOG4J2-1581: --- Summary: Warning should not display stacktrace Key: LOG4J2-1581 URL: https://issues.apache.org/jira/browse/LOG4J2-1581 Project: Log4j 2 Issue Type: Improvement

[jira] [Created] (LOG4J2-1582) Warning should not display stacktrace

Remko Popma created LOG4J2-1582: --- Summary: Warning should not display stacktrace Key: LOG4J2-1582 URL: https://issues.apache.org/jira/browse/LOG4J2-1582 Project: Log4j 2 Issue Type: Improvement

[jira] [Closed] (LOG4J2-1582) Warning should not display stacktrace

[ https://issues.apache.org/jira/browse/LOG4J2-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1582. --- Resolution: Fixed Fixed in master in commit 01cc155. > Warning should not display stacktrace > -

[jira] [Reopened] (LOG4J2-1582) Warning should not display stacktrace

[ https://issues.apache.org/jira/browse/LOG4J2-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1582: - There are two places doing error handling in Interpolater, and I fixed only one. Need to fix the oth

Re: OS-based dynamic configuration file

I committed a first cut, see comments in https://issues.apache.org/jira/browse/LOG4J2-1578 Gary On Mon, Sep 12, 2016 at 11:40 PM, Ralph Goers wrote: > Yes, it returns the key. Remember, a Route can dynamically create an > Appender so it isn’t required to be a reference. At the same time we can

[jira] [Commented] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488950#comment-15488950 ] Ralph Goers commented on LOG4J2-1578: - Yeah, I didn't think about the fact that it wo

[jira] [Comment Edited] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489021#comment-15489021 ] Gary Gregory edited comment on LOG4J2-1578 at 9/14/16 1:23 AM:

[jira] [Commented] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489021#comment-15489021 ] Gary Gregory commented on LOG4J2-1578: -- OK, I fixed the test, thanks for the tip.

Jenkins build became unstable: Log4j 2.x #2307

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-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489147#comment-15489147 ] Remko Popma commented on LOG4J2-1349: - TODO after further review: * rename GarbageFre

[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&focusedCommentId=15489171#comment-15489171 ] Gary Gregory commented on LOG4J2-1349: -- I wondering if we could switch terminology i

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

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-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489286#comment-15489286 ] Ralph Goers commented on LOG4J2-1578: - EventLogger should not be a problem. If Log4j

[jira] [Commented] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489319#comment-15489319 ] Gary Gregory commented on LOG4J2-1578: -- Roger that! > RoutingAppender can be config

Fwd: Jenkins build is still unstable: Log4j 2.x #2308

Got a real test failure potentially? https://builds.apache.org/job/Log4j%202.x/2308/org.apache.logging.log4j$log4j-core/testReport/org.apache.logging.log4j.core.async/AsyncLoggerAllThreadContextImplementationsTest/testAsyncLogWritesToLog_5_/ -- Forwarded message -- From: Apache Je

[jira] [Updated] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1578: - Description: RoutingAppender can be configured with scripts. h2. Use Case What I need to do is

[jira] [Updated] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1578: - Description: RoutingAppender can be configured with scripts. h2. Use Case What I need to do is

Fwd: [2/2] logging-log4j2 git commit: Deprecate factory method in favor of a builder.

If you use @Required on an array, it checks for non-null and non-empty. Works on strings, collections, and maps with the same semantics. -- Forwarded message -- From: Date: 13 September 2016 at 22:59 Subject: [2/2] logging-log4j2 git commit: Deprecate factory method in favor of a

Re: [2/2] logging-log4j2 git commit: Deprecate factory method in favor of a builder.

Good to know, I'll add that. But... we still need the check in the builders for programmatic configurations. Gary On Tue, Sep 13, 2016 at 9:11 PM, Matt Sicker wrote: > If you use @Required on an array, it checks for non-null and non-empty. > Works on strings, collections, and maps with the same

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

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

Re: logging-log4j2 git commit: [LOG4J2-1578] RoutingAppender can be configured with scripts. Add Script in a Routes element.

Gary, RoutingAppender calls routes.getPattern(). Wouldn’t it make sense for the Routes class to execute the script in the call to getPattern and return the result if there is a script? Ralph > On Sep 13, 2016, at 10:00 PM, ggreg...@apache.org wrote: > > Repository: logging-log4j2 > Updated B

[jira] [Comment Edited] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489505#comment-15489505 ] Gary Gregory edited comment on LOG4J2-1578 at 9/14/16 5:47 AM:

[jira] [Commented] (LOG4J2-1578) RoutingAppender can be configured with scripts

[ https://issues.apache.org/jira/browse/LOG4J2-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489505#comment-15489505 ] Gary Gregory commented on LOG4J2-1578: -- The {{Script}} with the {{Routes}} is in Git

Re: logging-log4j2 git commit: [LOG4J2-1578] RoutingAppender can be configured with scripts. Add Script in a Routes element.

On Tue, Sep 13, 2016 at 10:33 PM, Ralph Goers wrote: > Gary, > > RoutingAppender calls routes.getPattern(). Wouldn’t it make sense for the > Routes class to execute the script in the call to getPattern and return the > result if there is a script? > That's what Routes.getPattern() does (see thi

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

I have not seen that one before :-( Gary On Tue, Sep 13, 2016 at 8:55 PM, Matt Sicker wrote: > Got a real test failure potentially? > > https://builds.apache.org/job/Log4j%202.x/2308/org.apache. > logging.log4j$log4j-core/testReport/org.apache.logging.log4j.core.async/ > AsyncLoggerAllThreadCon

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

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-1051) NoClassDefFoundError when starting app on Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489566#comment-15489566 ] Lukasz Lenart commented on LOG4J2-1051: --- I'm again seeing the same problem in logs

[jira] [Commented] (LOG4J2-1051) NoClassDefFoundError when starting app on Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489597#comment-15489597 ] Lukasz Lenart commented on LOG4J2-1051: --- Problem is here {code:java} /** *

[jira] [Commented] (LOG4J2-1051) NoClassDefFoundError when starting app on Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489618#comment-15489618 ] Lukasz Lenart commented on LOG4J2-1051: --- As far I understand is due to introducing