[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] [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] [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] [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] [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] [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] [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] [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] [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] [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-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-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] [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] [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-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-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] [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] [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] [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] [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] [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-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] [Commented] (LOG4J2-3351) JDBC Appender not working for consecutive log events with OracleDB

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory commented on LOG4J2-3351: - Please run your use case with DEBUG on for Log4j

[jira] [Comment Edited] (LOG4J2-3351) JDBC Appender not working for consecutive log events with OracleDB

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory edited comment on LOG4J2-3351 at 2/1/22, 7:03 PM: --

[jira] [Comment Edited] (LOG4J2-3351) JDBC Appender not working for consecutive log events with OracleDB

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory edited comment on LOG4J2-3351 at 2/1/22, 7:04 PM: --

[jira] [Comment Edited] (LOG4J2-3351) JDBC Appender not working for consecutive log events with OracleDB

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory edited comment on LOG4J2-3351 at 2/1/22, 7:04 PM: --

[jira] [Resolved] (LOG4J2-3352) Log4j 1.2 bridge API hard codes the Syslog Host and port to localhost:514

[ https://issues.apache.org/jira/browse/LOG4J2-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3352. - Resolution: Information Provided > Log4j 1.2 bridge API hard codes the Syslog Host and

[jira] [Resolved] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3383. - Resolution: Information Provided > JMS Log deserialization is failing on jboss eap

[jira] [Updated] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3383: Affects Version/s: 2.10.0 > JMS Log deserialization is failing on jboss eap after upgrade

[jira] [Comment Edited] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484742#comment-17484742 ] Gary D. Gregory edited comment on LOG4J2-3372 at 2/1/22, 4:23 PM: -- It

[jira] [Commented] (LOG4J2-3390) AppenderSkeleton missing from log4j-1.2-api-2.3.2 bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486519#comment-17486519 ] Gary D. Gregory commented on LOG4J2-3390: - The best bridge version of the code is in 2.17.1 and

[jira] [Commented] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483926#comment-17483926 ] Gary D. Gregory commented on LOG4J2-3372: - It looks like the console appender builds a bad

[jira] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372 ] Gary D. Gregory deleted comment on LOG4J2-3372: - was (Author: garydgregory): It looks like the console appender builds a bad default pattern layout: It uses UTF-8 instead of the

[jira] [Commented] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483928#comment-17483928 ] Gary D. Gregory commented on LOG4J2-3372: - It looks like this was supposed to be fixed by

[jira] [Commented] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483930#comment-17483930 ] Gary D. Gregory commented on LOG4J2-3372: - In your console, try using a TrueType font like

[jira] [Comment Edited] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

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

[jira] [Commented] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484363#comment-17484363 ] Gary D. Gregory commented on LOG4J2-3372: - [~ppkarwasz]  See my comment above RE console fonts.

[jira] [Commented] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484742#comment-17484742 ] Gary D. Gregory commented on LOG4J2-3372: - It seems a console appender should specify its

[jira] [Commented] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484740#comment-17484740 ] Gary D. Gregory commented on LOG4J2-3372: - Ah, right, and if you want this to work from an IDE,

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485260#comment-17485260 ] Gary D. Gregory commented on LOG4J2-3383: - Hello [~leor.ami...@hsntech.com] I do not see

[jira] [Comment Edited] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

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

[jira] [Comment Edited] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3391: Summary: Add optional additional fields to NoSQLAppender (was: NoSQLAppender additional

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

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3391: Fix Version/s: (was: 2.16.0) > Add optional additional fields to NoSQLAppender >

[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=17488522#comment-17488522 ] Gary D. Gregory commented on LOG4J2-3396: - Would you provide a PR on GitHub with a test that

[jira] [Comment Edited] (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=17488550#comment-17488550 ] Gary D. Gregory edited comment on LOG4J2-3391 at 2/8/22, 2:16 AM: --

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

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3391. - Fix Version/s: 2.17.2 Resolution: Fixed > Add optional additional fields to

[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=17488550#comment-17488550 ] Gary D. Gregory commented on LOG4J2-3391: - [~ugurlu]  Please test git master or a

[jira] [Resolved] (LOG4J2-3392) AppenderLoggingException logging any exception to a MongoDB Appender

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

[jira] [Updated] (LOG4J2-3392) NoSQLAppender mongodb out of box exception support

[ https://issues.apache.org/jira/browse/LOG4J2-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3392: Summary: NoSQLAppender mongodb out of box exception support (was: NoSQLAppender mongodb4

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

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487545#comment-17487545 ] Gary D. Gregory commented on LOG4J2-3391: - Hello [~ugurlu]  Where do the values for such fields

[jira] [Comment Edited] (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=17488550#comment-17488550 ] Gary D. Gregory edited comment on LOG4J2-3391 at 2/8/22, 1:52 PM: --

[jira] [Resolved] (LOG4J2-2715) JDBCAppender commits to the DB a JTA RollbackOnly transaction and causes DB inconsistency

[ https://issues.apache.org/jira/browse/LOG4J2-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-2715. - Fix Version/s: 2.17.2 Resolution: Fixed I updated the site documentation but the

[jira] [Commented] (LOG4J2-3390) AppenderSkeleton missing from log4j-1.2-api-2.3.2 bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487708#comment-17487708 ] Gary D. Gregory commented on LOG4J2-3390: - Hi [~dwivedv]  TBH w you, I've put in as much time

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

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488268#comment-17488268 ] Gary D. Gregory commented on LOG4J2-3391: - I should be able to put some time into this soon-ish.

[jira] [Comment Edited] (LOG4J2-3391) NoSQLAppender additional fields

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488268#comment-17488268 ] Gary D. Gregory edited comment on LOG4J2-3391 at 2/7/22, 5:09 PM: -- I

[jira] [Comment Edited] (LOG4J2-3391) NoSQLAppender additional fields

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488268#comment-17488268 ] Gary D. Gregory edited comment on LOG4J2-3391 at 2/7/22, 5:09 PM: -- I

[jira] [Assigned] (LOG4J2-3391) NoSQLAppender additional fields

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3391: --- Assignee: Gary D. Gregory > NoSQLAppender additional fields >

[jira] [Commented] (LOG4J2-3317) After 2.17.1 upgarde, Route appenders with dynamic file writing are not working .

[ https://issues.apache.org/jira/browse/LOG4J2-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489469#comment-17489469 ] Gary D. Gregory commented on LOG4J2-3317: - Sounds like we better have a unit test that covers

[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

[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) NoSQLAppender additional fields

[ https://issues.apache.org/jira/browse/LOG4J2-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487758#comment-17487758 ] Gary D. Gregory commented on LOG4J2-3391: - Hi [~ugurlu]  What does your current Log4j

[jira] [Updated] (LOG4J2-3392) AppenderLoggingException logging any exception to a MongoDB Appender

[ https://issues.apache.org/jira/browse/LOG4J2-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3392: Summary: AppenderLoggingException logging any exception to a MongoDB Appender (was:

[jira] [Updated] (LOG4J2-3392) Exception logging an exception with to MongoDB Appender

[ https://issues.apache.org/jira/browse/LOG4J2-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3392: Summary: Exception logging an exception with to MongoDB Appender (was: NoSQLAppender

[jira] [Assigned] (LOG4J2-3392) NoSQLAppender mongodb4 out of box exception support

[ https://issues.apache.org/jira/browse/LOG4J2-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3392: --- Assignee: Gary D. Gregory > NoSQLAppender mongodb4 out of box exception support >

[jira] [Commented] (LOG4J2-3394) The 'rootLogger=${sys:root.logger:-INFO,console}' does not work

[ https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487514#comment-17487514 ] Gary D. Gregory commented on LOG4J2-3394: - This looks wrong rootLogger =

[jira] [Closed] (LOG4J2-3392) AppenderLoggingException logging any exception to a MongoDB Appender

[ https://issues.apache.org/jira/browse/LOG4J2-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-3392. --- > AppenderLoggingException logging any exception to a MongoDB Appender >

[jira] [Commented] (LOG4J2-3381) Programmatically configuring Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484639#comment-17484639 ] Gary D. Gregory commented on LOG4J2-3381: - You can try 2.17.2-SNAPSHOT where I recently added

[jira] [Comment Edited] (LOG4J2-3381) Programmatically configuring Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484639#comment-17484639 ] Gary D. Gregory edited comment on LOG4J2-3381 at 1/31/22, 12:26 PM:

[jira] [Commented] (LOG4J2-3381) Programmatically configuring Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484677#comment-17484677 ] Gary D. Gregory commented on LOG4J2-3381: - Snapshots are here:

[jira] [Updated] (LOG4J2-3380) Log4j syslog appender misses writing the 1st event after syslog service is restarted

[ https://issues.apache.org/jira/browse/LOG4J2-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3380: Affects Version/s: 2.17.1 > Log4j syslog appender misses writing the 1st event after

[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=17477816#comment-17477816 ] Gary D. Gregory commented on LOG4J2-3022: - [~stefanwendelmann]  How did you deal with your

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:45 PM: ---

[jira] [Comment Edited] (LOG4J2-3235) Exception: Invalid byte tag in constant pool: 19 for module-info.class Java 7

[ https://issues.apache.org/jira/browse/LOG4J2-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459915#comment-17459915 ] Gary D. Gregory edited comment on LOG4J2-3235 at 1/18/22, 12:24 PM:

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:28 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:47 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:46 PM: ---

[jira] [Assigned] (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 reassigned LOG4J2-3340: --- Assignee: Gary D. Gregory > StatusLogger's log Level cannot be changed as

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:24 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:29 PM: ---

[jira] [Work started] (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 ] Work on LOG4J2-3340 started by Gary D. Gregory. --- > StatusLogger's log Level cannot be changed as advertised >

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:37 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:37 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:43 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:45 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/18/22, 1:46 PM: ---

[jira] [Resolved] (LOG4J2-3122) Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level.

[ https://issues.apache.org/jira/browse/LOG4J2-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3122. - Fix Version/s: 2.17.0 Resolution: Fixed No reply from OP, see my previous

[jira] [Commented] (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:comment-tabpanel=17477832#comment-17477832 ] Gary D. Gregory commented on LOG4J2-3340: - Note: In StatusLogger, we have: this.logger = new

[jira] [Commented] (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:comment-tabpanel=17478060#comment-17478060 ] Gary D. Gregory commented on LOG4J2-3340: - Great explanation [~rgoers] , TY. The bottom line

[jira] [Updated] (LOG4J2-3347) Test failure in TypeConverterRegistryTest (master only)

[ https://issues.apache.org/jira/browse/LOG4J2-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3347: Description: [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:

[jira] [Created] (LOG4J2-3347) Test failure in TypeConverterRegistryTest (master only)

Gary D. Gregory created LOG4J2-3347: --- Summary: Test failure in TypeConverterRegistryTest (master only) Key: LOG4J2-3347 URL: https://issues.apache.org/jira/browse/LOG4J2-3347 Project: Log4j 2

[jira] [Commented] (LOG4J2-3348) Upgrade path from Log4j 1 to latest version of Log4j

[ https://issues.apache.org/jira/browse/LOG4J2-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478215#comment-17478215 ] Gary D. Gregory commented on LOG4J2-3348: - Hello [~delatejera]  Please read

[jira] [Commented] (LOG4J2-1792) Support property substitution when reading Log4j 1.x property config files

[ https://issues.apache.org/jira/browse/LOG4J2-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477503#comment-17477503 ] Gary D. Gregory commented on LOG4J2-1792: - Right, this was fixed under a different ticket for

[jira] [Commented] (LOG4J2-3354) Publish an SBOM with Log4j

[ https://issues.apache.org/jira/browse/LOG4J2-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479761#comment-17479761 ] Gary D. Gregory commented on LOG4J2-3354: - What is the difference with the BOM POM we already

<    1   2   3   4   5   >