[jira] [Commented] (LOG4J2-599) Support lambda functions (or similar) for log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13964547#comment-13964547 ] Nick Williams commented on LOG4J2-599: -- I would disagree with the notion that we are

[jira] [Assigned] (LOG4J2-474) MongoDBProvider won't work with databases that don't have authentication set up

[ https://issues.apache.org/jira/browse/LOG4J2-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-474: Assignee: Nick Williams MongoDBProvider won't work with databases that don't have

[jira] [Commented] (LOG4J2-474) MongoDBProvider won't work with databases that don't have authentication set up

[ https://issues.apache.org/jira/browse/LOG4J2-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911208#comment-13911208 ] Nick Williams commented on LOG4J2-474: -- I'll take care of this, Tal. Thanks for

[jira] [Commented] (LOG4J2-536) Project Depencies page has no content

[ https://issues.apache.org/jira/browse/LOG4J2-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899307#comment-13899307 ] Nick Williams commented on LOG4J2-536: -- H. This might be a Maven bug. The

[jira] [Commented] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894616#comment-13894616 ] Nick Williams commented on LOG4J2-529: -- Remko, here's your problem: {code:xml}?xml

[jira] [Commented] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894841#comment-13894841 ] Nick Williams commented on LOG4J2-529: -- I still can't duplicate this. I downloaded

[jira] [Commented] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894853#comment-13894853 ] Nick Williams commented on LOG4J2-529: -- I just tried a different approach and it

[jira] [Commented] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894889#comment-13894889 ] Nick Williams commented on LOG4J2-529: -- Yes, {{webapp30.war}} won't work in Tomcat

[jira] [Closed] (LOG4J2-422) DriverManager for JDBC Appender should have argument for explicit Driver class

[ https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams closed LOG4J2-422. Closing because not an issue anymore. DriverManager for JDBC Appender should have argument for

[jira] [Resolved] (LOG4J2-422) DriverManager for JDBC Appender should have argument for explicit Driver class

[ https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-422. -- Resolution: Fixed Fix Version/s: 2.0-rc1 This issue is fixed with r1565838. However,

[jira] [Assigned] (LOG4J2-442) Log4j2 Database insert problem in Websphere

[ https://issues.apache.org/jira/browse/LOG4J2-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-442: Assignee: Nick Williams Log4j2 Database insert problem in Websphere

[jira] [Assigned] (LOG4J2-489) Should JPADatabaseManager being using so many transactions?

[ https://issues.apache.org/jira/browse/LOG4J2-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-489: Assignee: Nick Williams Should JPADatabaseManager being using so many transactions?

[jira] [Assigned] (LOG4J2-457) JDBCAppender does not release JDBC connections to the connection pool when WAR/EAR is stopped

[ https://issues.apache.org/jira/browse/LOG4J2-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-457: Assignee: Nick Williams JDBCAppender does not release JDBC connections to the connection

[jira] [Resolved] (LOG4J2-438) JDBCDatabaseManager does not send commit command

[ https://issues.apache.org/jira/browse/LOG4J2-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-438. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed with r1565858 and r1565878. The database

[jira] [Resolved] (LOG4J2-407) JDBCAppender cannot recover from loss of database connectivity

[ https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-407. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed with r1565858 and r1565878. The database

[jira] [Resolved] (LOG4J2-442) Log4j2 Database insert problem in Websphere

[ https://issues.apache.org/jira/browse/LOG4J2-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-442. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed with r1565858 and r1565878. The database

[jira] [Resolved] (LOG4J2-489) Should JPADatabaseManager being using so many transactions?

[ https://issues.apache.org/jira/browse/LOG4J2-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-489. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed with r1565858 and r1565878. The database

[jira] [Resolved] (LOG4J2-457) JDBCAppender does not release JDBC connections to the connection pool when WAR/EAR is stopped

[ https://issues.apache.org/jira/browse/LOG4J2-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-457. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed with r1565858 and r1565878. The database

[jira] [Assigned] (LOG4J2-475) MongoDBConnection is broken because it uses addDecodingHook instead of addEncodingHook

[ https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-475: Assignee: Nick Williams MongoDBConnection is broken because it uses addDecodingHook

[jira] [Resolved] (LOG4J2-475) MongoDBConnection is broken because it uses addDecodingHook instead of addEncodingHook

[ https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-475. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed with r1565889. Based it off of Matt's

[jira] [Resolved] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-444. -- Resolution: Not A Problem Assignee: Nick Williams According to the [EclipseLink logging

[jira] [Commented] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894172#comment-13894172 ] Nick Williams commented on LOG4J2-529: -- Remko, I can't reproduce it. Works fine for

[jira] [Commented] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13888026#comment-13888026 ] Nick Williams commented on LOG4J2-500: -- It can be both. If a web application has the

[jira] [Reopened] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reopened LOG4J2-323: -- Remko, Nulling out the reference to the {{ThreadLocal}} is not enough (in fact, it's not even

[jira] [Resolved] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-323. -- Resolution: Fixed Fixed with r1562688. Please verify and close. ThreadLocal-leak on tomcat

[jira] [Commented] (LOG4J2-522) Split Logger interface in two with named level methods (info, warn, ...) in the subinterface.

[ https://issues.apache.org/jira/browse/LOG4J2-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886359#comment-13886359 ] Nick Williams commented on LOG4J2-522: -- -0: Paul has suggested we hold off on Using

[jira] [Commented] (LOG4J2-512) Log4j2 need to support Asynchronous Servlets/ Servlet 3.0 while automatically starting, and configurable to initialize and de-initialize loggers

[ https://issues.apache.org/jira/browse/LOG4J2-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885050#comment-13885050 ] Nick Williams commented on LOG4J2-512: -- Documentation updated with r1562365. Log4j2

[jira] [Commented] (LOG4J2-508) Add new Levels: NOTICE, DIAG, VERBOSE.

[ https://issues.apache.org/jira/browse/LOG4J2-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885054#comment-13885054 ] Nick Williams commented on LOG4J2-508: -- Can we close this as won't fix now, or are we

[jira] [Commented] (LOG4J2-492) MalformedObjectNameException: Invalid escape sequence... under Jetty

[ https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885056#comment-13885056 ] Nick Williams commented on LOG4J2-492: -- Remko, what's the status on this? I see that

[jira] [Commented] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885059#comment-13885059 ] Nick Williams commented on LOG4J2-444: -- Hemri, it occurred to me that you could mean

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging exceptions with Log4J2 in Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885070#comment-13885070 ] Nick Williams commented on LOG4J2-245: -- Max, I cannot replicate this in Java 1.7.0_45

[jira] [Updated] (LOG4J2-242) Make Messages more fluent

[ https://issues.apache.org/jira/browse/LOG4J2-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams updated LOG4J2-242: - Attachment: LOG4J2-242.patch I meant to attach this patch ages ago and never did it. These are

[jira] [Resolved] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-359. -- Resolution: Fixed This is fixed with r1561933. Unfortunately, WebLogic is simply not spec

[jira] [Resolved] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-344. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Sorry for the delay. This has been fixed with

[jira] [Resolved] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-409. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Thanks for the help identifying the problem

[jira] [Commented] (LOG4J2-410) java.io.NotSerializableException: org.slf4j.impl.SLF4JLogger

[ https://issues.apache.org/jira/browse/LOG4J2-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883792#comment-13883792 ] Nick Williams commented on LOG4J2-410: -- Should we take some action on this before

[jira] [Assigned] (LOG4J2-512) Log4j2 need to support Asynchronous Servlets/ Servlet 3.0 while automatically starting, and configurable to initialize and de-initialize loggers

[ https://issues.apache.org/jira/browse/LOG4J2-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-512: Assignee: Nick Williams Log4j2 need to support Asynchronous Servlets/ Servlet 3.0 while

[jira] [Commented] (LOG4J2-452) Log4j2 should not automatically start in Servlet 3.0

[ https://issues.apache.org/jira/browse/LOG4J2-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883845#comment-13883845 ] Nick Williams commented on LOG4J2-452: -- Partially fixed with r1561956 in that the

[jira] [Resolved] (LOG4J2-512) Log4j2 need to support Asynchronous Servlets/ Servlet 3.0 while automatically starting, and configurable to initialize and de-initialize loggers

[ https://issues.apache.org/jira/browse/LOG4J2-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-512. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed with r1561956. This exposes the web

[jira] [Commented] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883857#comment-13883857 ] Nick Williams commented on LOG4J2-500: -- Remko, have you had a chance to look at this

[jira] [Resolved] (LOG4J2-452) Log4j2 should not automatically start in Servlet 3.0

[ https://issues.apache.org/jira/browse/LOG4J2-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-452. -- Resolution: Fixed Fix Version/s: 2.0-rc1 The rest of this has been fixed with r1561958,

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861703#comment-13861703 ] Nick Williams commented on LOG4J2-479: -- In my opinion, we need to take one of two

[jira] [Comment Edited] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861703#comment-13861703 ] Nick Williams edited comment on LOG4J2-479 at 1/3/14 5:40 PM: --

[jira] [Commented] (LOG4J2-41) Extensible Log Level

[ https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831753#comment-13831753 ] Nick Williams commented on LOG4J2-41: - So I hate to reopen old wounds, but I'm going to

[jira] [Assigned] (LOG4J2-438) JDBCDatabaseManager does not send commit command

[ https://issues.apache.org/jira/browse/LOG4J2-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-438: Assignee: Nick Williams JDBCDatabaseManager does not send commit command

[jira] [Assigned] (LOG4J2-424) JDBCAppender: Add support for data types other then String

[ https://issues.apache.org/jira/browse/LOG4J2-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-424: Assignee: Nick Williams JDBCAppender: Add support for data types other then String

[jira] [Assigned] (LOG4J2-422) DriverManager for JDBC Appender should have argument for explicit Driver class

[ https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reassigned LOG4J2-422: Assignee: Nick Williams DriverManager for JDBC Appender should have argument for explicit

[jira] [Commented] (LOG4J2-422) DriverManager for JDBC Appender should have argument for explicit Driver class

[ https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792675#comment-13792675 ] Nick Williams commented on LOG4J2-422: -- It sounds like you are using a driver that is

[jira] [Commented] (LOG4J2-422) DriverManager for JDBC Appender should have argument for explicit Driver class

[ https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792922#comment-13792922 ] Nick Williams commented on LOG4J2-422: -- H. That's odd. Can you tell me a bit

[jira] [Commented] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774598#comment-13774598 ] Nick Williams commented on LOG4J2-409: -- Thanks for reporting this, Frank. Looks like

[jira] [Updated] (LOG4J2-407) JDBCAppender cannot recover from loss of database connectivity

[ https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams updated LOG4J2-407: - Assignee: Nick Williams JDBCAppender cannot recover from loss of database connectivity

[jira] [Commented] (LOG4J2-406) JMX MBeans are not being unregistered when a tomcat web application that uses log4j is undeployed, leading to a permgen memory leak.

[ https://issues.apache.org/jira/browse/LOG4J2-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772120#comment-13772120 ] Nick Williams commented on LOG4J2-406: -- The {{ServletContextListener}} correctly

[jira] [Commented] (LOG4J2-403) MongoDB appender, username and password should be optional.

[ https://issues.apache.org/jira/browse/LOG4J2-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770506#comment-13770506 ] Nick Williams commented on LOG4J2-403: -- I'll let some of the other guys weight in

[jira] [Comment Edited] (LOG4J2-330) NoSQLAppender cannot insert log event to MongoDB

[ https://issues.apache.org/jira/browse/LOG4J2-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770507#comment-13770507 ] Nick Williams edited comment on LOG4J2-330 at 9/18/13 6:46 AM:

[jira] [Updated] (LOG4J2-330) NoSQLAppender cannot insert log event to MongoDB

[ https://issues.apache.org/jira/browse/LOG4J2-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams updated LOG4J2-330: - Fix Version/s: (was: 2.0-beta9) NoSQLAppender cannot insert log event to MongoDB

[jira] [Commented] (LOG4J2-330) NoSQLAppender cannot insert log event to MongoDB

[ https://issues.apache.org/jira/browse/LOG4J2-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770507#comment-13770507 ] Nick Williams commented on LOG4J2-330: -- **head desk** That was a stupid mistake on

[jira] [Reopened] (LOG4J2-330) NoSQLAppender cannot insert log event to MongoDB

[ https://issues.apache.org/jira/browse/LOG4J2-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reopened LOG4J2-330: -- NoSQLAppender cannot insert log event to MongoDB

[jira] [Commented] (LOG4J2-322) Endless loop in ThrowableProxy.getCurrentStack

[ https://issues.apache.org/jira/browse/LOG4J2-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761467#comment-13761467 ] Nick Williams commented on LOG4J2-322: -- Excellent! Good to hear.

[jira] [Closed] (LOG4J2-322) Endless loop in ThrowableProxy.getCurrentStack

[ https://issues.apache.org/jira/browse/LOG4J2-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams closed LOG4J2-322. Endless loop in ThrowableProxy.getCurrentStack --

[jira] [Resolved] (LOG4J2-394) ClassLoaderContextSelector logging WARN messages

[ https://issues.apache.org/jira/browse/LOG4J2-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-394. -- Resolution: Duplicate ClassLoaderContextSelector logging WARN messages

[jira] [Commented] (LOG4J2-394) ClassLoaderContextSelector logging WARN messages

[ https://issues.apache.org/jira/browse/LOG4J2-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759240#comment-13759240 ] Nick Williams commented on LOG4J2-394: -- Because it is. This is caused by the

[jira] [Commented] (LOG4J2-394) ClassLoaderContextSelector logging WARN messages

[ https://issues.apache.org/jira/browse/LOG4J2-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759221#comment-13759221 ] Nick Williams commented on LOG4J2-394: -- I'm betting this is a web application?

[jira] [Comment Edited] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756535#comment-13756535 ] Nick Williams edited comment on LOG4J2-293 at 9/3/13 11:45 AM:

[jira] [Commented] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756535#comment-13756535 ] Nick Williams commented on LOG4J2-293: -- Point taken that there are improvements to be

[jira] [Comment Edited] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756535#comment-13756535 ] Nick Williams edited comment on LOG4J2-293 at 9/3/13 11:45 AM:

[jira] [Comment Edited] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756535#comment-13756535 ] Nick Williams edited comment on LOG4J2-293 at 9/3/13 11:46 AM:

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755535#comment-13755535 ] Nick Williams commented on LOG4J2-359: -- The problem is purely in documentation. The

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755546#comment-13755546 ] Nick Williams commented on LOG4J2-359: -- Okay. I think I understand something that

[jira] [Resolved] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-359. -- Resolution: Fixed Fix Version/s: 2.0-beta9 Thanks for the patch. I tweaked it slightly

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755572#comment-13755572 ] Nick Williams commented on LOG4J2-359: -- 1. No, it would not be valid to specify the

[jira] [Comment Edited] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755572#comment-13755572 ] Nick Williams edited comment on LOG4J2-359 at 8/31/13 6:24 PM:

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755625#comment-13755625 ] Nick Williams commented on LOG4J2-359: -- So. Many. Questions. And stop editing

[jira] [Reopened] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reopened LOG4J2-293: -- As instructed in the mailing list conversation you linked to, can you enable logging the

[jira] [Resolved] (LOG4J2-322) Endless loop in ThrowableProxy.getCurrentStack

[ https://issues.apache.org/jira/browse/LOG4J2-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-322. -- Resolution: Fixed Fix Version/s: 2.0-beta9 This has been fixed with trunk. Could you

[jira] [Resolved] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-359. -- Resolution: Duplicate Duplicate of LOG4J2-293. Log4jServletContextListener

[jira] [Issue Comment Deleted] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams updated LOG4J2-359: - Comment: was deleted (was: Duplicate of LOG4J2-293.) Log4jServletContextListener does not

[jira] [Reopened] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reopened LOG4J2-359: -- Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[jira] [Comment Edited] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755244#comment-13755244 ] Nick Williams edited comment on LOG4J2-359 at 8/30/13 11:16 PM:

[jira] [Resolved] (LOG4J2-357) log4jConfiguration via log4j.xml on classpath

[ https://issues.apache.org/jira/browse/LOG4J2-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-357. -- Resolution: Duplicate Duplicate of LOG4J2-293. log4jConfiguration via

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755244#comment-13755244 ] Nick Williams commented on LOG4J2-359: -- Shouldn't have closed this as duplicate.

[jira] [Commented] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755251#comment-13755251 ] Nick Williams commented on LOG4J2-293: -- Thanks for looking into and, possibly (I

[jira] [Comment Edited] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755251#comment-13755251 ] Nick Williams edited comment on LOG4J2-293 at 8/30/13 11:22 PM:

[jira] [Comment Edited] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755280#comment-13755280 ] Nick Williams edited comment on LOG4J2-293 at 8/31/13 12:09 AM:

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755281#comment-13755281 ] Nick Williams commented on LOG4J2-359: -- Your IDE has reformatted the JavaDoc and Java

[jira] [Commented] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755280#comment-13755280 ] Nick Williams commented on LOG4J2-293: -- Your IDE has reformatted the JavaDoc and Java

[jira] [Resolved] (LOG4J2-358) NoSQLAppender using MongoDB provider ignores username and password attributes

[ https://issues.apache.org/jira/browse/LOG4J2-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-358. -- Resolution: Fixed Fixed in next release. You can also get the latest from trunk and compile

[jira] [Commented] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742934#comment-13742934 ] Nick Williams commented on LOG4J2-362: -- That diagram is extremely clear and helpful,

[jira] [Commented] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742948#comment-13742948 ] Nick Williams commented on LOG4J2-362: -- Looks better! I think JIRA allows you to

[jira] [Commented] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742955#comment-13742955 ] Nick Williams commented on LOG4J2-362: -- There are actually several feature requests

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742618#comment-13742618 ] Nick Williams commented on LOG4J2-344: -- The stack trace in question can _*ONLY*_

[jira] [Created] (LOG4J2-358) NoSQLAppender using MongoDB provider ignores username and password attributes

Nick Williams created LOG4J2-358: Summary: NoSQLAppender using MongoDB provider ignores username and password attributes Key: LOG4J2-358 URL: https://issues.apache.org/jira/browse/LOG4J2-358 Project:

[jira] [Comment Edited] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742657#comment-13742657 ] Nick Williams edited comment on LOG4J2-344 at 8/16/13 10:20 PM:

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742657#comment-13742657 ] Nick Williams commented on LOG4J2-344: -- I thought about it, but doing so makes me

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742668#comment-13742668 ] Nick Williams commented on LOG4J2-359: -- Thanks for the thorough bug report. This may

[jira] [Updated] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams updated LOG4J2-359: - Assignee: Nick Williams Log4jServletContextListener does not work on Weblogic 12.1.1 (12c)

[jira] [Comment Edited] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742668#comment-13742668 ] Nick Williams edited comment on LOG4J2-359 at 8/16/13 10:27 PM:

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742672#comment-13742672 ] Nick Williams commented on LOG4J2-344: -- Keir, just for kicks, can you also post your

[jira] [Commented] (LOG4J2-359) Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version 2.5

[ https://issues.apache.org/jira/browse/LOG4J2-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742680#comment-13742680 ] Nick Williams commented on LOG4J2-359: -- Oh. Haha. I missed that part, somehow.

[jira] [Resolved] (LOG4J2-339) Infinit loop in ThrowableProxy

[ https://issues.apache.org/jira/browse/LOG4J2-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-339. -- Resolution: Duplicate Infinit loop in ThrowableProxy --

[jira] [Commented] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener

[ https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728557#comment-13728557 ] Nick Williams commented on LOG4J2-293: -- # Just to double-check, you're using Beta8,

  1   2   3   >