[jira] [Comment Edited] (LOG4J2-3231) JndiManager.isJndiEnabled generates a call to NetUtils.getLocalIps

[ https://issues.apache.org/jira/browse/LOG4J2-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459587#comment-17459587 ] Gary D. Gregory edited comment on LOG4J2-3231 at 12/15/21, 1:12 AM:

[jira] [Commented] (LOG4J2-3231) JndiManager.isJndiEnabled generates a call to NetUtils.getLocalIps

[ https://issues.apache.org/jira/browse/LOG4J2-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459587#comment-17459587 ] Gary D. Gregory commented on LOG4J2-3231: - Hello [~phongn]  Thank you for your report. May you

[jira] [Commented] (LOG4J2-3230) Certain strings can cause infinite recursion

[ https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459583#comment-17459583 ] Gary D. Gregory commented on LOG4J2-3230: - Hi [~BossColo]  You set the affect versions to "2.0,

[jira] [Commented] (LOG4J2-3230) Certain strings can cause infinite recursion

[ https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459571#comment-17459571 ] Gary D. Gregory commented on LOG4J2-3230: - I've improved on our Log4j string substitutor class

[jira] [Created] (LOG4J2-3228) Nothing should implement Serializable in Log4j 3

Gary D. Gregory created LOG4J2-3228: --- Summary: Nothing should implement Serializable in Log4j 3 Key: LOG4J2-3228 URL: https://issues.apache.org/jira/browse/LOG4J2-3228 Project: Log4j 2

[jira] [Commented] (LOG4J2-313) JNDI Lookup plugin support

[ https://issues.apache.org/jira/browse/LOG4J2-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459324#comment-17459324 ] Gary D. Gregory commented on LOG4J2-313: What end goal are you after? > JNDI Lookup plugin

[jira] [Commented] (LOG4J2-3201) Limit the protocols jNDI can use and restrict LDAP.

[ https://issues.apache.org/jira/browse/LOG4J2-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459271#comment-17459271 ] Gary D. Gregory commented on LOG4J2-3201: - The class

[jira] [Updated] (LOG4J2-3208) Disable JNDI by default

[ https://issues.apache.org/jira/browse/LOG4J2-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3208: Description: Dealing with CVE-2021-44228 has shown the JNDI has significant security

[jira] [Reopened] (LOG4J2-3208) Disable JNDI by default

[ https://issues.apache.org/jira/browse/LOG4J2-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reopened LOG4J2-3208: - > Disable JNDI by default > --- > > Key: LOG4J2-3208 >

[jira] [Closed] (LOG4J2-3208) Disable JNDI by default

[ https://issues.apache.org/jira/browse/LOG4J2-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-3208. --- Resolution: Fixed Fixed CVE ID in description. > Disable JNDI by default >

[jira] [Commented] (LOG4J2-3214) Update security page text for CVE-2021-44228

[ https://issues.apache.org/jira/browse/LOG4J2-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458513#comment-17458513 ] Gary D. Gregory commented on LOG4J2-3214: - The confusion is made worse as CVE-2021-4104 is a

[jira] [Commented] (LOG4J2-3219) CVE-2021-44228 on log4j version 1.2.17

[ https://issues.apache.org/jira/browse/LOG4J2-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458485#comment-17458485 ] Gary D. Gregory commented on LOG4J2-3219: - Hello [~ARUNNAIK]  No. Gary   > CVE-2021-44228 on

[jira] [Commented] (LOG4J2-3201) Limit the protocols jNDI can use and restrict LDAP.

[ https://issues.apache.org/jira/browse/LOG4J2-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458470#comment-17458470 ] Gary D. Gregory commented on LOG4J2-3201: - Yes, you can only update log4j-core but it will be

[jira] [Updated] (LOG4J2-3214) Update security page text for CVE-2021-44228

[ https://issues.apache.org/jira/browse/LOG4J2-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3214: Description: I propose to update the text for the mitigation section of CVE-2021-44228 on

[jira] [Commented] (LOG4J2-3214) Update security page text for CVE-2021-44228

[ https://issues.apache.org/jira/browse/LOG4J2-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458385#comment-17458385 ] Gary D. Gregory commented on LOG4J2-3214: - I made a couple of readability tweaks. > Update

[jira] [Updated] (LOG4J2-3214) Update security page text for CVE-2021-44228

[ https://issues.apache.org/jira/browse/LOG4J2-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3214: Summary: Update security page text for CVE-2021-44228 (was: update security page text

[jira] [Updated] (LOG4J2-3214) update security page text for CVE-2021-44228

[ https://issues.apache.org/jira/browse/LOG4J2-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3214: Description: I propose to update the text for the mitigation section of CVE-2021-44228 on

[jira] [Commented] (LOG4J2-3214) update security page text for CVE-2021-44228

[ https://issues.apache.org/jira/browse/LOG4J2-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458347#comment-17458347 ] Gary D. Gregory commented on LOG4J2-3214: - I would like to replace the "details" links with

[jira] [Commented] (LOG4J2-3205) OutputStreamManager.flushBuffer throw NoSuchMethodError ByteBuffer.clear

[ https://issues.apache.org/jira/browse/LOG4J2-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17457136#comment-17457136 ] Gary D. Gregory commented on LOG4J2-3205: - You MUST use Java 8 to target Java 8 in this case

[jira] [Commented] (LOG4J2-3199) Log4j2 - Strange behavior with Async Logger + JDBC Appender + Oracle DB

[ https://issues.apache.org/jira/browse/LOG4J2-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17451296#comment-17451296 ] Gary D. Gregory commented on LOG4J2-3199: - This feels like an issue on the DBMS side. A JDBC

[jira] [Commented] (LOG4J2-3198) Message lookups should be disabled by default

[ https://issues.apache.org/jira/browse/LOG4J2-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450500#comment-17450500 ] Gary D. Gregory commented on LOG4J2-3198: - +1 to disable lookups in messages by default.  User

[jira] [Commented] (LOG4J2-3140) Mongo4 appender stays in TimeOut

[ https://issues.apache.org/jira/browse/LOG4J2-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423392#comment-17423392 ] Gary D. Gregory commented on LOG4J2-3140: - Is it possible that the connection from Log4j goes

[jira] [Commented] (LOG4J2-3138) Define a custom model for a json layout for creating custom json logs output

[ https://issues.apache.org/jira/browse/LOG4J2-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405801#comment-17405801 ] Gary D. Gregory commented on LOG4J2-3138: - Can't edit my comment above! Adding: ok to break

[jira] [Commented] (LOG4J2-3138) Define a custom model for a json layout for creating custom json logs output

[ https://issues.apache.org/jira/browse/LOG4J2-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405799#comment-17405799 ] Gary D. Gregory commented on LOG4J2-3138: - For 3.0, IMO, breaking compatibility is Ok,

[jira] [Commented] (LOG4J2-3145) Cannot see JDBC error message

[ https://issues.apache.org/jira/browse/LOG4J2-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404387#comment-17404387 ] Gary D. Gregory commented on LOG4J2-3145: - I suppose this should be an error log event, not a

[jira] [Commented] (LOG4J2-3140) Mongo4 appender stays in TimeOut

[ https://issues.apache.org/jira/browse/LOG4J2-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402585#comment-17402585 ] Gary D. Gregory commented on LOG4J2-3140: - Please post your configuration file. > Mongo4

[jira] [Commented] (LOG4J2-3133) The slf4j (1.7) implementation is missing some expected methods

[ https://issues.apache.org/jira/browse/LOG4J2-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17393182#comment-17393182 ] Gary D. Gregory commented on LOG4J2-3133: - Not that Slf4j happily breaks binary compatibility

[jira] [Resolved] (LOG4J2-3131) Attempting to call getExtendedStackTraceAsString() after deserializing JSON LogEvent results in a NPE

[ https://issues.apache.org/jira/browse/LOG4J2-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3131. - Fix Version/s: 3.0.0. 2.15.0 Resolution: Fixed > Attempting

[jira] [Commented] (LOG4J2-3131) Attempting to call getExtendedStackTraceAsString() after deserializing JSON LogEvent results in a NPE

[ https://issues.apache.org/jira/browse/LOG4J2-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388752#comment-17388752 ] Gary D. Gregory commented on LOG4J2-3131: - [~a...@adam-long.net] I fixed this in the git branch

[jira] [Assigned] (LOG4J2-3131) Attempting to call getExtendedStackTraceAsString() after deserializing JSON LogEvent results in a NPE

[ https://issues.apache.org/jira/browse/LOG4J2-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3131: --- Assignee: Gary D. Gregory > Attempting to call getExtendedStackTraceAsString()

[jira] [Commented] (LOG4J2-3131) Attempting to call getExtendedStackTraceAsString() after deserializing JSON LogEvent results in a NPE

[ https://issues.apache.org/jira/browse/LOG4J2-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388212#comment-17388212 ] Gary D. Gregory commented on LOG4J2-3131: - May you post the stack trace here please? >

[jira] [Commented] (LOG4J2-3113) Support Supplier<> in varargs log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378081#comment-17378081 ] Gary D. Gregory commented on LOG4J2-3113: - IMO, favoring the JRE for logging is a mistake, you

[jira] [Commented] (LOG4J2-3117) Log rollover throws AccessControlException if called from an unprivileged context

[ https://issues.apache.org/jira/browse/LOG4J2-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17377638#comment-17377638 ] Gary D. Gregory commented on LOG4J2-3117: - Note: The Security Manager is going away:

[jira] [Commented] (LOG4J2-3113) Support Supplier<> in varargs log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371671#comment-17371671 ] Gary D. Gregory commented on LOG4J2-3113: - It's going to care if you pass instances around ;-)

[jira] [Commented] (LOG4J2-3113) Support Supplier<> in varargs log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371485#comment-17371485 ] Gary D. Gregory commented on LOG4J2-3113: - Would you be able to provide a PR on GitHub? >

[jira] [Commented] (LOG4J2-3113) Support Supplier<> in varargs log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370573#comment-17370573 ] Gary D. Gregory commented on LOG4J2-3113: - Note that this is currently supported via a custom

[jira] [Commented] (LOG4J2-2803) Create standardized scopes and dependency injection API

[ https://issues.apache.org/jira/browse/LOG4J2-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357954#comment-17357954 ] Gary D. Gregory commented on LOG4J2-2803: - I might be playing devil's advocate here but why

[jira] [Comment Edited] (LOG4J2-2803) Create standardized scopes and dependency injection API

[ https://issues.apache.org/jira/browse/LOG4J2-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357952#comment-17357952 ] Gary D. Gregory edited comment on LOG4J2-2803 at 6/5/21, 10:03 PM: --- Is

[jira] [Commented] (LOG4J2-2803) Create standardized scopes and dependency injection API

[ https://issues.apache.org/jira/browse/LOG4J2-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357952#comment-17357952 ] Gary D. Gregory commented on LOG4J2-2803: - Is an unstated goal here to support exisiting

[jira] [Commented] (LOG4J2-3095) Category.setLevel should accept null value

[ https://issues.apache.org/jira/browse/LOG4J2-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17353854#comment-17353854 ] Gary D. Gregory commented on LOG4J2-3095: - In git master and release-2.x branches.   >

[jira] [Assigned] (LOG4J2-3095) Category.setLevel should accept null value

[ https://issues.apache.org/jira/browse/LOG4J2-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3095: --- Assignee: Gary D. Gregory > Category.setLevel should accept null value >

[jira] [Comment Edited] (LOG4J2-3100) log4j2 lots of final class, forbid extend class, why log4j allow extend class but log4j2 not?

[ https://issues.apache.org/jira/browse/LOG4J2-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17353734#comment-17353734 ] Gary D. Gregory edited comment on LOG4J2-3100 at 5/29/21, 11:31 AM:

[jira] [Commented] (LOG4J2-3100) log4j2 lots of final class, forbid extend class, why log4j allow extend class but log4j2 not?

[ https://issues.apache.org/jira/browse/LOG4J2-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17353734#comment-17353734 ] Gary D. Gregory commented on LOG4J2-3100: - I agree with [~vy]. It's better to provide API

[jira] [Commented] (LOG4J2-3089) JsonTemplateLayoutNullEventDelimiterTest sporadically fails on Windows

[ https://issues.apache.org/jira/browse/LOG4J2-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339775#comment-17339775 ] Gary D. Gregory commented on LOG4J2-3089: - We should be able to use port 0 as an ephemeral port

[jira] [Resolved] (LOG4J2-2505) Let JDBC PoolingDriverConnectionSource with Apache Commons DBCP configure a PoolableConnectionFactory

[ https://issues.apache.org/jira/browse/LOG4J2-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-2505. - Resolution: Fixed > Let JDBC PoolingDriverConnectionSource with Apache Commons DBCP

[jira] [Commented] (LOG4J2-2505) Let JDBC PoolingDriverConnectionSource with Apache Commons DBCP configure a PoolableConnectionFactory

[ https://issues.apache.org/jira/browse/LOG4J2-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1713#comment-1713 ] Gary D. Gregory commented on LOG4J2-2505: - Yes, I am done for now. The Collection of String

[jira] [Commented] (LOG4J2-3066) Improve Socket Appender error handling

[ https://issues.apache.org/jira/browse/LOG4J2-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315950#comment-17315950 ] Gary D. Gregory commented on LOG4J2-3066: - Should this be made to work in cunjunction with the

[jira] [Commented] (LOG4J2-1902) log4j2-web does not disable shutdownHook

[ https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304065#comment-17304065 ] Gary D. Gregory commented on LOG4J2-1902: - Note that 2.14.1 has some changes in this area.  >

[jira] [Commented] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

[ https://issues.apache.org/jira/browse/LOG4J2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291658#comment-17291658 ] Gary D. Gregory commented on LOG4J2-3026: - Hi [~rgoers] There is no {{CompositeConfiguration}}

[jira] [Commented] (LOG4J2-3027) TcpSocketServer in latest log4j2 version (2.14.0)

[ https://issues.apache.org/jira/browse/LOG4J2-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291082#comment-17291082 ] Gary D. Gregory commented on LOG4J2-3027: - While the serial feature of the server sample is

[jira] [Commented] (LOG4J2-3027) TcpSocketServer in latest log4j2 version (2.14.0)

[ https://issues.apache.org/jira/browse/LOG4J2-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290938#comment-17290938 ] Gary D. Gregory commented on LOG4J2-3027: - Yes, clone it, build it. > TcpSocketServer in latest

[jira] [Commented] (LOG4J2-3027) TcpSocketServer in latest log4j2 version (2.14.0)

[ https://issues.apache.org/jira/browse/LOG4J2-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290915#comment-17290915 ] Gary D. Gregory commented on LOG4J2-3027: - That code has moved to

[jira] [Commented] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

[ https://issues.apache.org/jira/browse/LOG4J2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290662#comment-17290662 ] Gary D. Gregory commented on LOG4J2-3026: - I'll take a look in the AM, I do see what you mean.

[jira] [Resolved] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

[ https://issues.apache.org/jira/browse/LOG4J2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3026. - Fix Version/s: 3.0.0 Resolution: Fixed In git branches: {{release-2.x}},

[jira] [Commented] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

[ https://issues.apache.org/jira/browse/LOG4J2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290269#comment-17290269 ] Gary D. Gregory commented on LOG4J2-3026: - Nope, that's not enough, it's the {{WatchManager}} 

[jira] [Updated] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

[ https://issues.apache.org/jira/browse/LOG4J2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3026: Description: The {{WatchManager}} does not stop its {{ConfigurationScheduler}} thereby

[jira] [Updated] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

[ https://issues.apache.org/jira/browse/LOG4J2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3026: Description: The {{WatchManager}} does not stop its {{ConfigurationScheduler}} thereby

[jira] [Work started] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

[ https://issues.apache.org/jira/browse/LOG4J2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3026 started by Gary D. Gregory. --- > WatchManager does not stop its ConfigurationScheduler thereby leaking

[jira] [Created] (LOG4J2-3026) WatchManager does not stop its ConfigurationScheduler thereby leaking a thread

Gary D. Gregory created LOG4J2-3026: --- Summary: WatchManager does not stop its ConfigurationScheduler thereby leaking a thread Key: LOG4J2-3026 URL: https://issues.apache.org/jira/browse/LOG4J2-3026

[jira] [Commented] (LOG4J2-3022) AsyncLogger with JDBC Appender PoolingDriver not concurrent

[ https://issues.apache.org/jira/browse/LOG4J2-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286867#comment-17286867 ] Gary D. Gregory commented on LOG4J2-3022: - It looks like we synchronize here:

[jira] [Commented] (LOG4J2-3023) Implement compression in JsonTemplateLayout

[ https://issues.apache.org/jira/browse/LOG4J2-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286638#comment-17286638 ] Gary D. Gregory commented on LOG4J2-3023: - And if you want the most flexibility, use Apache

[jira] [Comment Edited] (LOG4J2-3019) HtmlLayoutTest.testLayoutWithDatePatternFixedFormat test fails on windows

[ https://issues.apache.org/jira/browse/LOG4J2-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284286#comment-17284286 ] Gary D. Gregory edited comment on LOG4J2-3019 at 2/13/21, 8:49 PM: --- OK

[jira] [Commented] (LOG4J2-3019) HtmlLayoutTest.testLayoutWithDatePatternFixedFormat test fails on windows

[ https://issues.apache.org/jira/browse/LOG4J2-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284286#comment-17284286 ] Gary D. Gregory commented on LOG4J2-3019: - OK for me: {noformat} mvn test -pl log4j-core

[jira] [Commented] (LOG4J2-3017) Groovy logging of GString with $ notation is very slow

[ https://issues.apache.org/jira/browse/LOG4J2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17283922#comment-17283922 ] Gary D. Gregory commented on LOG4J2-3017: - I would be concerned that the conversion happens too

[jira] [Commented] (LOG4J2-3019) HtmlLayoutTest.testLayoutWithDatePatternFixedFormat test fails on windows

[ https://issues.apache.org/jira/browse/LOG4J2-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17282646#comment-17282646 ] Gary D. Gregory commented on LOG4J2-3019: - [~vy] I'll try to get to it tonight. >

[jira] [Resolved] (LOG4J2-3014) Log4j1ConfigurationConverter on Windows produces "" at end of every line

[ https://issues.apache.org/jira/browse/LOG4J2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3014. - Fix Version/s: 3.0.0. 2.14.1 Resolution: Fixed >

[jira] [Commented] (LOG4J2-3014) Log4j1ConfigurationConverter on Windows produces "" at end of every line

[ https://issues.apache.org/jira/browse/LOG4J2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17277696#comment-17277696 ] Gary D. Gregory commented on LOG4J2-3014: - Fixed in branch {{release-2.x}}, {{master}} is to-do

[jira] [Work started] (LOG4J2-3014) Log4j1ConfigurationConverter on Windows produces "" at end of every line

[ https://issues.apache.org/jira/browse/LOG4J2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3014 started by Gary D. Gregory. --- > Log4j1ConfigurationConverter on Windows produces "" at end of every

[jira] [Assigned] (LOG4J2-3014) Log4j1ConfigurationConverter on Windows produces "" at end of every line

[ https://issues.apache.org/jira/browse/LOG4J2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3014: --- Assignee: Gary D. Gregory > Log4j1ConfigurationConverter on Windows produces "" at

[jira] [Commented] (LOG4J2-2988) SocketAppender is not able to reload key and certs

[ https://issues.apache.org/jira/browse/LOG4J2-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260491#comment-17260491 ] Gary D. Gregory commented on LOG4J2-2988: - Log4j already supports the notion of a "watch

[jira] [Commented] (LOG4J2-2989) Has Log4j2 a risk of losing logs for streaming towards a remote server when it cannot re-establish a connection towards the server?

[ https://issues.apache.org/jira/browse/LOG4J2-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259139#comment-17259139 ] Gary D. Gregory commented on LOG4J2-2989: - It sounds like the use case here is like what we have

[jira] [Commented] (LOG4J2-2982) Use {@systemProperty} javadoc tag

[ https://issues.apache.org/jira/browse/LOG4J2-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255155#comment-17255155 ] Gary D. Gregory commented on LOG4J2-2982: - That would require that we generate Javadocs with

[jira] [Resolved] (LOG4J2-2976) JdbcAppender composes an incorrect INSERT statement without a ColumnMapping element.

[ https://issues.apache.org/jira/browse/LOG4J2-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-2976. - Fix Version/s: 2.14.1 Resolution: Fixed > JdbcAppender composes an incorrect

[jira] [Commented] (LOG4J2-2976) JdbcAppender composes an incorrect INSERT statement without a ColumnMapping element.

[ https://issues.apache.org/jira/browse/LOG4J2-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17248639#comment-17248639 ] Gary D. Gregory commented on LOG4J2-2976: - [~aslancz] Thank you for your ticket. May you

[jira] [Updated] (LOG4J2-2976) JdbcAppender doesn't compose correct INSERT statement without a ColumnMapping element

[ https://issues.apache.org/jira/browse/LOG4J2-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-2976: Summary: JdbcAppender doesn't compose correct INSERT statement without a ColumnMapping

[jira] [Commented] (LOG4J2-2972) AsyncAppender thread gets killed with ThreadDeath exception

[ https://issues.apache.org/jira/browse/LOG4J2-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17247296#comment-17247296 ] Gary D. Gregory commented on LOG4J2-2972: - Please see my comment in github WRT lame names. >

[jira] [Commented] (LOG4J2-2970) Adding String return type of each log method

[ https://issues.apache.org/jira/browse/LOG4J2-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244562#comment-17244562 ] Gary D. Gregory commented on LOG4J2-2970: - Hi All: For me at work, the log-then-throw patten

[jira] [Commented] (LOG4J2-2969) NPE at getContextMap() in RingBufferLogEvent

[ https://issues.apache.org/jira/browse/LOG4J2-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243558#comment-17243558 ] Gary D. Gregory commented on LOG4J2-2969: - Does the error still occur in 2.14.0? > NPE at

[jira] [Commented] (LOG4J2-2964) Merge "packages" from several Configurations in Composite Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239390#comment-17239390 ] Gary D. Gregory commented on LOG4J2-2964: - [~rgoers] Should we start by marking packages as

[jira] [Commented] (LOG4J2-2964) Merge "packages" from several Configurations in Composite Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17233136#comment-17233136 ] Gary D. Gregory commented on LOG4J2-2964: - I agree with Ralph. > Merge "packages" from several

[jira] [Deleted] (LOG4J2-2960) Popular medicines for Erectile Dysfunction

[ https://issues.apache.org/jira/browse/LOG4J2-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory deleted LOG4J2-2960: > Popular medicines for Erectile Dysfunction > -- >

[jira] [Commented] (LOG4J2-2955) SizeBasedTriggeringPolicy with space between the number and the unit does not work e.g. 1 MB does not work but 1MB does work.

[ https://issues.apache.org/jira/browse/LOG4J2-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224907#comment-17224907 ] Gary D. Gregory commented on LOG4J2-2955: - I would not call this a bug unless we document that

[jira] [Commented] (LOG4J2-2937) Provide counters to measure log rate

[ https://issues.apache.org/jira/browse/LOG4J2-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205564#comment-17205564 ] Gary D. Gregory commented on LOG4J2-2937: - Would we want to count at the appender level as well

[jira] [Commented] (LOG4J2-2937) Provide counters to measure log rate

[ https://issues.apache.org/jira/browse/LOG4J2-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203542#comment-17203542 ] Gary D. Gregory commented on LOG4J2-2937: - Would counting be a feature a configuration would

[jira] [Comment Edited] (LOG4J2-2937) Provide counters to measure log rate

[ https://issues.apache.org/jira/browse/LOG4J2-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203275#comment-17203275 ] Gary D. Gregory edited comment on LOG4J2-2937 at 9/28/20, 2:50 PM: ---

[jira] [Commented] (LOG4J2-2937) Provide counters to measure log rate

[ https://issues.apache.org/jira/browse/LOG4J2-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203275#comment-17203275 ] Gary D. Gregory commented on LOG4J2-2937: - What are we talking about here, more concretely?

[jira] [Comment Edited] (LOG4J2-2909) Version Upgrade of log4j2 jars from 2.10.0 to 2.13.2 cause TPS degradation

[ https://issues.apache.org/jira/browse/LOG4J2-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177283#comment-17177283 ] Gary D. Gregory edited comment on LOG4J2-2909 at 8/13/20, 7:04 PM: ---

[jira] [Commented] (LOG4J2-2909) Version Upgrade of log4j2 jars from 2.10.0 to 2.13.2 cause TPS degradation

[ https://issues.apache.org/jira/browse/LOG4J2-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177283#comment-17177283 ] Gary D. Gregory commented on LOG4J2-2909: - You probably export this run, attache it here, so we

[jira] [Commented] (LOG4J2-2891) More DB Logging Support

[ https://issues.apache.org/jira/browse/LOG4J2-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156668#comment-17156668 ] Gary D. Gregory commented on LOG4J2-2891: - Use our JDBC Appender... it looks like Druid has JDBC

[jira] [Comment Edited] (LOG4J2-2864) Getting java.lang.ClassNotFoundException: com.mongodb.MongoClient while using mongodb-driver-sync(4.0.4) instead of mongo-java-driver

[ https://issues.apache.org/jira/browse/LOG4J2-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128120#comment-17128120 ] Gary D. Gregory edited comment on LOG4J2-2864 at 6/8/20, 10:11 AM: ---

[jira] [Commented] (LOG4J2-2864) Getting java.lang.ClassNotFoundException: com.mongodb.MongoClient while using mongodb-driver-sync(4.0.4) instead of mongo-java-driver

[ https://issues.apache.org/jira/browse/LOG4J2-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128120#comment-17128120 ] Gary D. Gregory commented on LOG4J2-2864: - The mongols 4 drivers break compatibility with

[jira] [Resolved] (LOG4J2-2848) Create module log4j-mongodb4 to use new major version 4 MongoDB driver

[ https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-2848. - Resolution: Fixed > Create module log4j-mongodb4 to use new major version 4 MongoDB

[jira] [Closed] (LOG4J2-2851) Drop log4j-mongodb2 module.

[ https://issues.apache.org/jira/browse/LOG4J2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-2851. --- Resolution: Fixed > Drop log4j-mongodb2 module. > --- > >

[jira] [Comment Edited] (LOG4J2-2848) Create module log4j-mongodb4 to use new major version 4 MongoDB driver

[ https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113174#comment-17113174 ] Gary D. Gregory edited comment on LOG4J2-2848 at 5/22/20, 7:18 PM: --- Hi

[jira] [Updated] (LOG4J2-2848) Create module log4j-mongodb4 to use new major version 4 MongoDB driver

[ https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-2848: Fix Version/s: 2.14.0 3.0.0 > Create module log4j-mongodb4 to use new

[jira] [Work started] (LOG4J2-2851) Drop log4j-mongodb2 module.

[ https://issues.apache.org/jira/browse/LOG4J2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2851 started by Gary D. Gregory. --- > Drop log4j-mongodb2 module. > --- > >

[jira] [Updated] (LOG4J2-2851) Drop log4j-mongodb2 module.

[ https://issues.apache.org/jira/browse/LOG4J2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-2851: Fix Version/s: 3.0.0 > Drop log4j-mongodb2 module. > --- > >

[jira] [Created] (LOG4J2-2851) Drop log4j-mongodb2 module.

Gary D. Gregory created LOG4J2-2851: --- Summary: Drop log4j-mongodb2 module. Key: LOG4J2-2851 URL: https://issues.apache.org/jira/browse/LOG4J2-2851 Project: Log4j 2 Issue Type: Task

[jira] [Commented] (LOG4J2-2848) Create module log4j-mongodb4 to use new major version 4 MongoDB driver

[ https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113174#comment-17113174 ] Gary D. Gregory commented on LOG4J2-2848: - Hi [~rgoers] I'm OK with dropping log4j-mongodb2. I

[jira] [Updated] (LOG4J2-2848) Create module log4j-mongodb4 to use new major version 4 MongoDB driver

[ https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-2848: Summary: Create module log4j-mongodb4 to use new major version 4 MongoDB driver (was:

<    1   2   3   4   5   >