[jira] [Commented] (LOGCXX-576) Logging DOAP file has an error

[ https://issues.apache.org/jira/browse/LOGCXX-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816430#comment-17816430 ] Gary D. Gregory commented on LOGCXX-576: Moving this issue to the LOGCXX Jira project. > Logging

[jira] [Moved] (LOGCXX-576) Logging DOAP file has an error

[ https://issues.apache.org/jira/browse/LOGCXX-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory moved LOGGING-184 to LOGCXX-576: Key: LOGCXX-576 (was: LOGGING-184) Affects

[jira] [Commented] (LOG4J2-3666) traceEntry() and traceExit() - Similar methods not there with INFO/DEBUG level?

[ https://issues.apache.org/jira/browse/LOG4J2-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750429#comment-17750429 ] Gary D. Gregory commented on LOG4J2-3666: - Because this is designed to "trace" coming in and out

[jira] [Commented] (LOG4J2-3662) Don't register JMX beans by default

[ https://issues.apache.org/jira/browse/LOG4J2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723141#comment-17723141 ] Gary D. Gregory commented on LOG4J2-3662: - Sounds reasonable to me. > Don't register JMX beans

[jira] [Commented] (LOG4J2-2092) Extended Throwable produces unnecessary long stack traces compared to standard stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17610089#comment-17610089 ] Gary D. Gregory commented on LOG4J2-2092: - That's the point of "extended" ;)  Perhaps we should

[jira] [Created] (LOG4J2-3599) Random failure in LoggerTest.flowTracingString_ObjectArray2

Gary D. Gregory created LOG4J2-3599: --- Summary: Random failure in LoggerTest.flowTracingString_ObjectArray2 Key: LOG4J2-3599 URL: https://issues.apache.org/jira/browse/LOG4J2-3599 Project: Log4j 2

[jira] [Resolved] (LOG4J2-3594) ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.ConsoleAppender for element Console:java.nio.charset.IllegalCharsetNameException: "fi

[ https://issues.apache.org/jira/browse/LOG4J2-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3594. - Fix Version/s: 2.19.0 Resolution: Duplicate > ERROR Could not create plugin of

[jira] [Commented] (LOG4J2-2148) CronTriggeringPolicy renaming behavior

[ https://issues.apache.org/jira/browse/LOG4J2-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17577975#comment-17577975 ] Gary D. Gregory commented on LOG4J2-2148: - Hi [~wlfbck]  Are you using 2.18.0?   >

[jira] [Commented] (LOG4J2-3568) ResolverUtil fails to extractPath for custom plugins in jar, if there are blanks in the path

[ https://issues.apache.org/jira/browse/LOG4J2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575800#comment-17575800 ] Gary D. Gregory commented on LOG4J2-3568: - A special case for space is not good enough because

[jira] [Commented] (LOG4J2-3533) Desired Log4j 2.17.x files not available

[ https://issues.apache.org/jira/browse/LOG4J2-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552205#comment-17552205 ] Gary D. Gregory commented on LOG4J2-3533: - Log4j 2 files are here:

[jira] [Commented] (LOG4J2-3500) Deadlock in Log4j

[ https://issues.apache.org/jira/browse/LOG4J2-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532762#comment-17532762 ] Gary D. Gregory commented on LOG4J2-3500: - Hello [~G1G4]  2.12.1 is a pretty old version. Would

[jira] [Commented] (LOG4J2-3498) Timestamp lacks micro and nano second precision on linux

[ https://issues.apache.org/jira/browse/LOG4J2-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532219#comment-17532219 ] Gary D. Gregory commented on LOG4J2-3498: - It looks like your project uses Java 11 so the JRE

[jira] [Commented] (LOG4J2-3498) Timestamp lacks micro and nano second precision on linux

[ https://issues.apache.org/jira/browse/LOG4J2-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532217#comment-17532217 ] Gary D. Gregory commented on LOG4J2-3498: - You should update your test to Log4j 2.17.2 to make

[jira] [Commented] (LOG4J2-3476) Support JUL ApiLogger::setLevel

[ https://issues.apache.org/jira/browse/LOG4J2-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522249#comment-17522249 ] Gary D. Gregory commented on LOG4J2-3476: - Ah, right. So the next question is why not add a

[jira] [Commented] (LOG4J2-3476) Support JUL ApiLogger::setLevel

[ https://issues.apache.org/jira/browse/LOG4J2-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522238#comment-17522238 ] Gary D. Gregory commented on LOG4J2-3476: - Since log4j-jul already has an optional dependency on

[jira] [Commented] (LOG4J2-3467) Update from Log4J 2.17.1 to 2.17.2 breaks application

[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519567#comment-17519567 ] Gary D. Gregory commented on LOG4J2-3467: - [~pkarwasz]  TL;DR: Please, no. I would say that

[jira] [Resolved] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3471. - Fix Version/s: 2.17.3 Resolution: Fixed [~rajeshn]  Thank you for your report.

[jira] [Updated] (LOG4J2-3471) log4j-1.2-api-2.17.2 throws NullPointerException while removing appender with name as null

[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3471: Summary: log4j-1.2-api-2.17.2 throws NullPointerException while removing appender with

[jira] [Updated] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3471: Summary: log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with

[jira] [Assigned] (LOG4J2-3471) log4j-1.2-api-2.17.2 throws exception while removing appender with name as null

[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3471: --- Assignee: Gary D. Gregory > log4j-1.2-api-2.17.2 throws exception while removing

[jira] [Assigned] (LOG4J2-3463) java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider: Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype

[ https://issues.apache.org/jira/browse/LOG4J2-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3463: --- Assignee: (was: Gary D. Gregory) > java.util.ServiceConfigurationError:

[jira] [Assigned] (LOG4J2-3463) java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider: Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype

[ https://issues.apache.org/jira/browse/LOG4J2-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3463: --- Assignee: Gary D. Gregory > java.util.ServiceConfigurationError:

[jira] [Commented] (LOG4J2-3467) Update from Log4J 2.17.1 to 2.17.2 breaks application

[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518282#comment-17518282 ] Gary D. Gregory commented on LOG4J2-3467: - I just need something I can drop in and test, for me,

[jira] [Commented] (LOG4J2-3467) Update from Log4J 2.17.1 to 2.17.2 breaks application

[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518262#comment-17518262 ] Gary D. Gregory commented on LOG4J2-3467: - What is the class path you use to run this program?

[jira] [Commented] (LOG4J2-3467) Update from Log4J 2.17.1 to 2.17.2 breaks application

[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518130#comment-17518130 ] Gary D. Gregory commented on LOG4J2-3467: - Thank you for your report. We need something to

[jira] [Resolved] (LOG4J2-3458) LocalizedMessage logs misleading errors on the console

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

[jira] [Updated] (LOG4J2-3458) LocalizedMessage logs misleading errors on the console

[ https://issues.apache.org/jira/browse/LOG4J2-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3458: Summary: LocalizedMessage logs misleading errors on the console (was: LocalizedMessage

[jira] [Updated] (LOG4J2-3458) LocalizedMessage logs misleading errors on the console.

[ https://issues.apache.org/jira/browse/LOG4J2-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3458: Summary: LocalizedMessage logs misleading errors on the console. (was: LocalizedMessage

[jira] [Updated] (LOG4J2-3458) LocalizedMessage logs misleading errors on the console\

[ https://issues.apache.org/jira/browse/LOG4J2-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3458: Summary: LocalizedMessage logs misleading errors on the console\ (was: LocalizedMessage

[jira] [Updated] (LOG4J2-3458) LocalizedMessage causes a lot of noise on the console

[ https://issues.apache.org/jira/browse/LOG4J2-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3458: Description: I have an app where we log data that is percent encoded through a localized

[jira] [Created] (LOG4J2-3458) LocalizedMessage causes a lot of noise on the console

Gary D. Gregory created LOG4J2-3458: --- Summary: LocalizedMessage causes a lot of noise on the console Key: LOG4J2-3458 URL: https://issues.apache.org/jira/browse/LOG4J2-3458 Project: Log4j 2

[jira] [Commented] (LOG4J2-2795) Make LogManager/LoggerContext creation time reasonable

[ https://issues.apache.org/jira/browse/LOG4J2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514812#comment-17514812 ] Gary D. Gregory commented on LOG4J2-2795: - Another use case that would benefit from faster

[jira] [Commented] (LOG4J2-3440) Log4j 1.2 bridge getAllAppenders() returns null enumeration

[ https://issues.apache.org/jira/browse/LOG4J2-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512040#comment-17512040 ] Gary D. Gregory commented on LOG4J2-3440: - It seems that we should do something that is a close

[jira] [Commented] (LOG4J2-3444) Log4j 1.2 Unsupported Flagging by Nessus

[ https://issues.apache.org/jira/browse/LOG4J2-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511458#comment-17511458 ] Gary D. Gregory commented on LOG4J2-3444: - I do not see that we have to get in between two

[jira] [Commented] (LOG4J2-3440) Log4j 1.2 bridge getAllAppenders() returns null enumeration

[ https://issues.apache.org/jira/browse/LOG4J2-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510697#comment-17510697 ] Gary D. Gregory commented on LOG4J2-3440: - For good or bad, I see this type of behavior all the

[jira] [Comment Edited] (LOG4J2-3440) Log4j 1.2 bridge getAllAppenders() returns null enumeration

[ https://issues.apache.org/jira/browse/LOG4J2-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510375#comment-17510375 ] Gary D. Gregory edited comment on LOG4J2-3440 at 3/22/22, 9:51 AM: --- Hi

[jira] [Commented] (LOG4J2-3440) Log4j 1.2 bridge getAllAppenders() returns null enumeration

[ https://issues.apache.org/jira/browse/LOG4J2-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510375#comment-17510375 ] Gary D. Gregory commented on LOG4J2-3440: - Hi all, The bridge code has greatly improved in

[jira] [Updated] (LOG4J2-3428) Update 3rd party dependencies for 2.17.3

[ https://issues.apache.org/jira/browse/LOG4J2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3428: Description: This ticket should only be closed when we release 2.17.3. The updated

[jira] [Updated] (LOG4J2-3428) Update 3rd party dependencies for 2.17.3

[ https://issues.apache.org/jira/browse/LOG4J2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3428: Description: This ticket should only be closed when we release 2.17.3. The updated

[jira] [Commented] (LOG4J2-3437) Log4j 1.x bridge Request to support programmatically configuring Log4j.

[ https://issues.apache.org/jira/browse/LOG4J2-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507798#comment-17507798 ] Gary D. Gregory commented on LOG4J2-3437: - FTR, the method is

[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=17507668#comment-17507668 ] Gary D. Gregory commented on LOG4J2-3019: - [~LKleeven] and all, Please verify the release-2,x

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

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

[jira] [Commented] (LOG4J2-3437) Log4j 1.x bridge Request to support programmatically configuring Log4j.

[ https://issues.apache.org/jira/browse/LOG4J2-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507506#comment-17507506 ] Gary D. Gregory commented on LOG4J2-3437: - Hi [~PoojaTheCoder]  Would you provide an example

[jira] [Comment Edited] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .

[ https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506867#comment-17506867 ] Gary D. Gregory edited comment on LOG4J2-3432 at 3/15/22, 11:48 AM:

[jira] [Comment Edited] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .

[ https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506867#comment-17506867 ] Gary D. Gregory edited comment on LOG4J2-3432 at 3/15/22, 11:48 AM:

[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .

[ https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506867#comment-17506867 ] Gary D. Gregory commented on LOG4J2-3432: - My POV is different obviously: if there is anything

[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .

[ https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506621#comment-17506621 ] Gary D. Gregory commented on LOG4J2-3432: - I asked because the current version should be the

[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .

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

[jira] [Resolved] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3423. - Resolution: Fixed > JAR file containing Log4j configuration isn't closed >

[jira] [Commented] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files

[ https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505376#comment-17505376 ] Gary D. Gregory commented on LOG4J2-3431: - [~TukeshK]  Note the solution in

[jira] [Commented] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files

[ https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505353#comment-17505353 ] Gary D. Gregory commented on LOG4J2-3431: - [~TukeshK] See the previous comment and  > log4j

[jira] [Updated] (LOG4J2-3428) Update 3rd party dependencies for 2.17.3

[ https://issues.apache.org/jira/browse/LOG4J2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3428: Description: This ticket should only be closed when we release 2.17.3. The updated

[jira] [Updated] (LOG4J2-3428) Update 3rd party dependencies for 2.17.3

[ https://issues.apache.org/jira/browse/LOG4J2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3428: Description: This ticket should only be closed when we release 2.17.3. The updated

[jira] [Updated] (LOG4J2-3428) Update 3rd party dependencies for 2.17.3

[ https://issues.apache.org/jira/browse/LOG4J2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3428: Description: The updated dependencies are: *

[jira] [Created] (LOG4J2-3428) Update 3rd party dependencies for 2.17.3

Gary D. Gregory created LOG4J2-3428: --- Summary: Update 3rd party dependencies for 2.17.3 Key: LOG4J2-3428 URL: https://issues.apache.org/jira/browse/LOG4J2-3428 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502006#comment-17502006 ] Gary D. Gregory commented on LOG4J2-3425: - I think we should close this ticket and open a new

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501038#comment-17501038 ] Gary D. Gregory commented on LOG4J2-3423: - I wonder if there is a JDK bug for that or it is has

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500951#comment-17500951 ] Gary D. Gregory commented on LOG4J2-3425: - Hm, do we want a new {{SocketChannelAppender}} so we

[jira] [Updated] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3425: External issue URL: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4031100 >

[jira] [Updated] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3425: Summary: Syslog appender lacks the SocketOptions setting (was: Syslog appender lacks the

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500899#comment-17500899 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 5:04 PM: --

[jira] [Resolved] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3425. - Fix Version/s: 2.17.3 Resolution: Fixed > Syslog appender lacks the

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500899#comment-17500899 ] Gary D. Gregory commented on LOG4J2-3425: - [~SkyCrawl]  Dang it, well that's lame, sorry about

[jira] [Commented] (LOG4J2-3424) JDBC Appender configuration properties not handled correctly after upgrading to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500887#comment-17500887 ] Gary D. Gregory commented on LOG4J2-3424: - [~ckozak] Any advice? It looks like raw value is from

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500866#comment-17500866 ] Gary D. Gregory edited comment on LOG4J2-3423 at 3/3/22, 4:48 PM: --

[jira] [Updated] (LOG4J2-3360) Document unsafe lookup usage patterns

[ https://issues.apache.org/jira/browse/LOG4J2-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3360: Fix Version/s: 2.17.3 (was: 2.17.2) > Document unsafe lookup usage

[jira] [Updated] (LOG4J2-3340) StatusLogger's log Level cannot be changed as advertised

[ https://issues.apache.org/jira/browse/LOG4J2-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3340: Fix Version/s: 2.17.3 (was: 2.17.2) > StatusLogger's log Level

[jira] [Resolved] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3423. - Fix Version/s: 2.17.3 Resolution: Fixed Fixed in git branch {{release-2.x}} and

[jira] [Work started] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3423 started by Gary D. Gregory. --- > JAR file containing Log4j configuration isn't closed >

[jira] [Assigned] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3423: --- Assignee: Gary D. Gregory > JAR file containing Log4j configuration isn't closed >

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500693#comment-17500693 ] Gary D. Gregory edited comment on LOG4J2-3423 at 3/3/22, 2:05 PM: -- The

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500747#comment-17500747 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 1:50 PM: --

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500747#comment-17500747 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 1:29 PM: --

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500747#comment-17500747 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 1:30 PM: --

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500747#comment-17500747 ] Gary D. Gregory commented on LOG4J2-3425: - [~SkyCrawl]  A Syslog Appender is a Socket Appender,

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500693#comment-17500693 ] Gary D. Gregory commented on LOG4J2-3423: - The url connection's setUseCaches can be called with

[jira] [Commented] (LOG4J2-3419) Unable to create custom logging level using log4j 2 Bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500686#comment-17500686 ] Gary D. Gregory commented on LOG4J2-3419: - [~ragini]  See my first comment and I should be able

[jira] [Commented] (LOG4J2-3419) Unable to create custom logging level using log4j 2 Bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499619#comment-17499619 ] Gary D. Gregory commented on LOG4J2-3419: - Hi [~ragini]  Would you provide a PR on GitHub with

[jira] [Commented] (LOG4J2-3421) Programmatic Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499515#comment-17499515 ] Gary D. Gregory commented on LOG4J2-3421: - [~sovikstepan]  Thank you for this report. Would

[jira] [Comment Edited] (LOG4J2-3417) Create JDBC appender for compatibility with v1

[ https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498835#comment-17498835 ] Gary D. Gregory edited comment on LOG4J2-3417 at 2/28/22, 10:47 AM:

[jira] [Commented] (LOG4J2-3417) Create JDBC appender for compatibility with v1

[ https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498835#comment-17498835 ] Gary D. Gregory commented on LOG4J2-3417: - Excellent. As long as we do reuse Log4j 2's runtime,

[jira] [Commented] (LOG4J2-3417) Create JDBC appender for compatibility with v1

[ https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498660#comment-17498660 ] Gary D. Gregory commented on LOG4J2-3417: - Internally the SQL for something like 

[jira] [Commented] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product

[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498134#comment-17498134 ] Gary D. Gregory commented on LOG4J2-3414: - [~PoojaTheCoder]  Please see

[jira] [Closed] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product

[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-3414. --- Resolution: Information Provided [~PoojaTheCoder] please subscribe to the user's mailing

[jira] [Commented] (LOG4J2-3396) ERROR Recursive call to appender mongodb with spring boot root logger

[ https://issues.apache.org/jira/browse/LOG4J2-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17496096#comment-17496096 ] Gary D. Gregory commented on LOG4J2-3396: - I am guessing there is a loop between slf4j and Log4j

[jira] (LOG4J2-3407) PropertiesConfiguration.parseAppender NPE when logger refers to non-existent appender

[ https://issues.apache.org/jira/browse/LOG4J2-3407 ] Gary D. Gregory deleted comment on LOG4J2-3407: - was (Author: garydgregory): I am guessing there is a loop between slf4j and Log4j as the MongoDB client depends on slf4j:

[jira] [Commented] (LOG4J2-3407) PropertiesConfiguration.parseAppender NPE when logger refers to non-existent appender

[ https://issues.apache.org/jira/browse/LOG4J2-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17496094#comment-17496094 ] Gary D. Gregory commented on LOG4J2-3407: - I am guessing there is a loop between slf4j and Log4j

[jira] [Resolved] (LOG4J2-3407) PropertiesConfiguration.parseAppender NPE when logger refers to non-existent appender

[ https://issues.apache.org/jira/browse/LOG4J2-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3407. - Fix Version/s: 2.17.2 Resolution: Fixed [~kennymacleod.atl]  In git branch

[jira] [Resolved] (LOG4J2-3410) Log4j 1.2 bridge throws a ClassCastException when logging a Map with non-String keys

[ https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3410. - Fix Version/s: 2.17.2 Resolution: Fixed Hi [~bcfsham] , Thank you for reporting

[jira] [Work started] (LOG4J2-3410) Log4j 1.2 bridge throws a ClassCastException when logging a Map with non-String keys

[ https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3410 started by Gary D. Gregory. --- > Log4j 1.2 bridge throws a ClassCastException when logging a Map with

[jira] [Assigned] (LOG4J2-3410) Log4j 1.2 bridge throws a ClassCastException when logging a Map with non-String keys

[ https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3410: --- Assignee: Gary D. Gregory > Log4j 1.2 bridge throws a ClassCastException when

[jira] [Updated] (LOG4J2-3410) Log4j 1.x Compatibility API - ClassCastException when logging a Map with non-String keys

[ https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3410: Summary: Log4j 1.x Compatibility API - ClassCastException when logging a Map with

[jira] [Updated] (LOG4J2-3410) Log4j 1.2 bridge throws a ClassCastException when logging a Map with non-String keys

[ https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3410: Summary: Log4j 1.2 bridge throws a ClassCastException when logging a Map with non-String

[jira] [Commented] (LOG4J2-3407) PropertiesConfiguration.parseAppender NPE when logger refers to non-existent appender

[ https://issues.apache.org/jira/browse/LOG4J2-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17494640#comment-17494640 ] Gary D. Gregory commented on LOG4J2-3407: - Yikes. I see 2 issues: give a better exception

[jira] [Commented] (LOG4J2-3407) PropertiesConfiguration.parseAppender NPE when logger refers to non-existent appender

[ https://issues.apache.org/jira/browse/LOG4J2-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17494575#comment-17494575 ] Gary D. Gregory commented on LOG4J2-3407: - Changing the default behavior is a bad idea IMO. Not

[jira] [Commented] (LOG4J2-3388) Migration from log4j1.x to log4j2.x

[ https://issues.apache.org/jira/browse/LOG4J2-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493208#comment-17493208 ] Gary D. Gregory commented on LOG4J2-3388: - Do you have whitespace at the end of the lines in the

[jira] [Commented] (LOG4J2-3328) Log4j 1.2 bridge does not support system properties in log4j.xml

[ https://issues.apache.org/jira/browse/LOG4J2-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491961#comment-17491961 ] Gary D. Gregory commented on LOG4J2-3328: - Hi [~john215], my guess is within one month. > Log4j

[jira] [Commented] (LOG4J2-3371) Log Injection Vulnerability exists in Log4j2 default configuration

[ https://issues.apache.org/jira/browse/LOG4J2-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490479#comment-17490479 ] Gary D. Gregory commented on LOG4J2-3371: - If we were to allow for stripping out control

[jira] [Commented] (LOG4J2-3391) Add optional additional fields to NoSQLAppender

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490271#comment-17490271 ] Gary D. Gregory commented on LOG4J2-3391: - [~ugurlu]  Give it another go and let me know... >

[jira] [Commented] (LOG4J2-3399) Release date for 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489856#comment-17489856 ] Gary D. Gregory commented on LOG4J2-3399: - A better place for this query is the user's mailing

  1   2   3   4   5   >