[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] [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] [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] [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-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-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] [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] [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] [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] [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] [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-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] [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=17487545#comment-17487545 ] Gary D. Gregory commented on LOG4J2-3391: - Hello [~ugurlu]  Where do the values for such fields

[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) 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] [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-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] [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-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] [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] [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] [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] [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] [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] [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] [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] [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] [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] [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-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] [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=17484639#comment-17484639 ] Gary D. Gregory commented on LOG4J2-3381: - You can try 2.17.2-SNAPSHOT where I recently added

[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-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] [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=17483930#comment-17483930 ] Gary D. Gregory commented on LOG4J2-3372: - In your console, try using a TrueType font like

[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] (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=17483926#comment-17483926 ] Gary D. Gregory commented on LOG4J2-3372: - It looks like the console appender builds a bad

[jira] [Resolved] (LOG4J2-3349) RollingFileAppenderBuilder in log4j1 bridge does not create the appender as in log4j1

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

[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=17481791#comment-17481791 ] Gary D. Gregory commented on LOG4J2-3219: - Please see

[jira] [Resolved] (LOG4J2-3364) Category in 1.2.17 implements AppenderAttachable but does not in v2 1.2 api

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

[jira] [Commented] (LOG4J2-3364) Category in 1.2.17 implements AppenderAttachable but does not in v2 1.2 api

[ https://issues.apache.org/jira/browse/LOG4J2-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481080#comment-17481080 ] Gary D. Gregory commented on LOG4J2-3364: - Hello [~iouwon]  Please try 2.17.2-SNAPSHOT where

[jira] [Assigned] (LOG4J2-3359) Facility and priority missing in Syslog message when Syslog log appender and pattern layout is used with log4j1-2 bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3359: --- Assignee: Gary D. Gregory > Facility and priority missing in Syslog message when

[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=17480305#comment-17480305 ] Gary D. Gregory commented on LOG4J2-3328: - Probably maybe possibly in 2 weeks or thereabouts, no

[jira] [Commented] (LOG4J2-3359) Facility and priority missing in Syslog message when Syslog log appender and pattern layout is used with log4j1-2 bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480064#comment-17480064 ] Gary D. Gregory commented on LOG4J2-3359: - Hi [~TukeshK]  I recently fixed some issues in this

[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

[jira] [Resolved] (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:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3348. - Resolution: Information Provided > Upgrade path from Log4j 1 to latest version of Log4j

[jira] [Closed] (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:all-tabpanel ] Gary D. Gregory closed LOG4J2-3348. --- > Upgrade path from Log4j 1 to latest version of Log4j >

[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=17478060#comment-17478060 ] Gary D. Gregory edited comment on LOG4J2-3340 at 1/20/22, 1:05 PM: ---

[jira] [Commented] (LOG4J2-3350) Routing appender does not expand nested variables

[ https://issues.apache.org/jira/browse/LOG4J2-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478816#comment-17478816 ] Gary D. Gregory commented on LOG4J2-3350: - Oops, I linked the wrong issue. > Routing appender

[jira] [Closed] (LOG4J2-3350) Routing appender does not expand nested variables

[ https://issues.apache.org/jira/browse/LOG4J2-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-3350. --- Fix Version/s: 2.17.2 Resolution: Fixed [~stemaio]  Please search Jira before

[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: Affects Version/s: 3.0.0 > Test failure in TypeConverterRegistryTest (master only) >

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

[ https://issues.apache.org/jira/browse/LOG4J2-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478687#comment-17478687 ] Gary D. Gregory commented on LOG4J2-3347: - [~mattsicker] If you use the ticket number in the

[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] [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-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] [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] [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] [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: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: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: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:29 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:24 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] [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] [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-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-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] [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-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] [Closed] (LOG4J2-3205) OutputStreamManager.flushBuffer throw NoSuchMethodError ByteBuffer.clear

[ https://issues.apache.org/jira/browse/LOG4J2-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-3205. --- Resolution: Not A Bug Closing as not a bug. > OutputStreamManager.flushBuffer throw

[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=17476838#comment-17476838 ] Gary D. Gregory commented on LOG4J2-3199: - Hi [~jacob2221]  Can you try this with 2.17.1? TY.

[jira] [Resolved] (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:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3328. - Fix Version/s: 2.17.2 Resolution: Fixed Hello [~paulcooper]  I fixed this issue

[jira] [Updated] (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:all-tabpanel ] Gary D. Gregory updated LOG4J2-3328: Summary: Log4j 1.2 bridge does not support system properties in log4j.xml (was: Log4j

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

[ https://issues.apache.org/jira/browse/LOG4J2-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3328: --- Assignee: Gary D. Gregory > Log4j bridge does not support system properties in

[jira] [Commented] (LOG4J2-3323) Breaking change in AbstractManager

[ https://issues.apache.org/jira/browse/LOG4J2-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17475022#comment-17475022 ] Gary D. Gregory commented on LOG4J2-3323: - Hi [~rschmitt]  Make sure guys are on 2.17.1 though.

[jira] [Resolved] (LOG4J2-3330) Configurator.setLevel not fetching the correct LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3330. - Fix Version/s: 2.17.2 Resolution: Fixed > Configurator.setLevel not fetching the

[jira] [Commented] (LOG4J2-3330) Configurator.setLevel not fetching the correct LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474546#comment-17474546 ] Gary D. Gregory commented on LOG4J2-3330: - [~mlemnaru]  Please try the git branch *release-2.x*

[jira] [Comment Edited] (LOG4J2-3330) Configurator.setLevel not fetching the correct LoggerContext

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

[jira] [Commented] (LOG4J2-3330) Configurator.setLevel not fetching the correct LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474497#comment-17474497 ] Gary D. Gregory commented on LOG4J2-3330: - The problems applies to the following APIs in

[jira] [Work started] (LOG4J2-3330) Configurator.setLevel not fetching the correct LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3330 started by Gary D. Gregory. --- > Configurator.setLevel not fetching the correct LoggerContext >

[jira] [Assigned] (LOG4J2-3330) Configurator.setLevel not fetching the correct LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3330: --- Assignee: Gary D. Gregory > Configurator.setLevel not fetching the correct

[jira] [Comment Edited] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

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

[jira] [Commented] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

[ https://issues.apache.org/jira/browse/LOG4J2-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472697#comment-17472697 ] Gary D. Gregory commented on LOG4J2-3319: - Hm, this is now giving me pause. I'm not sure why the

[jira] [Comment Edited] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

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

[jira] [Commented] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

[ https://issues.apache.org/jira/browse/LOG4J2-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472147#comment-17472147 ] Gary D. Gregory commented on LOG4J2-3319: - I just approved the buld runs on GitHub, so let's

<    1   2   3   4   5   >