[jira] [Commented] (LOG4J2-3628) Migrate from maven-changes-plugin to a merge-conflict-free Markdown-based solution

[ https://issues.apache.org/jira/browse/LOG4J2-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630585#comment-17630585 ] Carter Kozak commented on LOG4J2-3628: -- This sounds great to me, the system very nearly matches

[jira] [Commented] (LOG4J2-3623) Application went unresponsive because of log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624017#comment-17624017 ] Carter Kozak commented on LOG4J2-3623: -- This looks a lot like LOG4J2-3619 Can you please provide a

[jira] [Commented] (LOG4J2-3619) Log4j stops logging when the log message contains a java.lang.StackOverflowError

[ https://issues.apache.org/jira/browse/LOG4J2-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623213#comment-17623213 ] Carter Kozak commented on LOG4J2-3619: -- That would be ideal, if you could reproduce the failure! Is

[jira] [Commented] (LOG4J2-3619) Log4j stops logging when the log message contains a java.lang.StackOverflowError

[ https://issues.apache.org/jira/browse/LOG4J2-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17621324#comment-17621324 ] Carter Kozak commented on LOG4J2-3619: -- Is there any chance you could create a minimal reproducer

[jira] [Commented] (LOG4J2-2623) log4j-to-slf4j: Messages are formatted twice if there happen to be a `{}` in the parameters

[ https://issues.apache.org/jira/browse/LOG4J2-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572637#comment-17572637 ] Carter Kozak commented on LOG4J2-2623: -- I believe this is a duplicate of

[jira] [Commented] (LOG4J2-3560) Logger$PrivateConfig.filter(Level, Marker, String) allocates empty varargs array

[ https://issues.apache.org/jira/browse/LOG4J2-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572064#comment-17572064 ] Carter Kozak commented on LOG4J2-3560: -- Thanks for the fix! I've applied it to both release-2.x and

[jira] [Resolved] (LOG4J2-3560) Logger$PrivateConfig.filter(Level, Marker, String) allocates empty varargs array

[ https://issues.apache.org/jira/browse/LOG4J2-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3560. -- Resolution: Fixed > Logger$PrivateConfig.filter(Level, Marker, String) allocates empty

[jira] [Closed] (LOG4J2-3560) Logger$PrivateConfig.filter(Level, Marker, String) allocates empty varargs array

[ https://issues.apache.org/jira/browse/LOG4J2-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3560. > Logger$PrivateConfig.filter(Level, Marker, String) allocates empty varargs > array >

[jira] [Updated] (LOG4J2-3560) Logger$PrivateConfig.filter(Level, Marker, String) allocates empty varargs array

[ https://issues.apache.org/jira/browse/LOG4J2-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-3560: - Fix Version/s: 2.18.1 Affects Version/s: 2.18.0 > Logger$PrivateConfig.filter(Level,

[jira] [Assigned] (LOG4J2-3560) Logger$PrivateConfig.filter(Level, Marker, String) allocates empty varargs array

[ https://issues.apache.org/jira/browse/LOG4J2-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3560: Assignee: Carter Kozak > Logger$PrivateConfig.filter(Level, Marker, String) allocates

[jira] [Commented] (LOG4J2-3505) Threads get stuck inside TimeoutBlockingWaitStrategy when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536875#comment-17536875 ] Carter Kozak commented on LOG4J2-3505: -- It's potentially odd that there are two {{AsyncLogger}}

[jira] [Commented] (LOG4J2-3505) Threads get stuck inside TimeoutBlockingWaitStrategy when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536864#comment-17536864 ] Carter Kozak commented on LOG4J2-3505: -- Can you share some details about your

[jira] [Commented] (LOG4J2-3478) Base64 lookup doesn't work with system property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531717#comment-17531717 ] Carter Kozak commented on LOG4J2-3478: -- It looks like that was added to the documentation in this

[jira] [Commented] (LOG4J2-3480) Changed behaviour (regression) in 2.17.2 lookup plugin or string interpolation

[ https://issues.apache.org/jira/browse/LOG4J2-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530920#comment-17530920 ] Carter Kozak commented on LOG4J2-3480: -- I think you may want to update the lookup plugin to

[jira] [Commented] (LOG4J2-3478) Base64 lookup doesn't work with system property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530910#comment-17530910 ] Carter Kozak commented on LOG4J2-3478: -- I don't believe we have a base64 lookup in log4j2. If we

[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=17522494#comment-17522494 ] Carter Kozak commented on LOG4J2-3476: -- I agree with the api/implementation separation and would

[jira] [Comment Edited] (LOG4J2-3470) Expressions in property values are not expanded anymore

[ https://issues.apache.org/jira/browse/LOG4J2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518850#comment-17518850 ] Carter Kozak edited comment on LOG4J2-3470 at 4/7/22 12:26 PM: --- Sorry,

[jira] [Reopened] (LOG4J2-3470) Expressions in property values are not expanded anymore

[ https://issues.apache.org/jira/browse/LOG4J2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reopened LOG4J2-3470: -- > Expressions in property values are not expanded anymore >

[jira] [Closed] (LOG4J2-3470) Expressions in property values are not expanded anymore

[ https://issues.apache.org/jira/browse/LOG4J2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3470. Resolution: Duplicate This is a duplicate of https://issues.apache.org/jira/browse/LOG4J2-3424,

[jira] [Closed] (LOG4J2-3434) Property is not populating "value"

[ https://issues.apache.org/jira/browse/LOG4J2-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3434. Resolution: Duplicate This is a duplicate of https://issues.apache.org/jira/browse/LOG4J2-3424,

[jira] [Commented] (LOG4J2-3459) Reduce use of class static initialization blocks

[ https://issues.apache.org/jira/browse/LOG4J2-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515611#comment-17515611 ] Carter Kozak commented on LOG4J2-3459: -- I’ve used jmh for this sort of thing using oneshot mode

[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503605#comment-17503605 ] Carter Kozak commented on LOG4J2-3345: -- The System.Logger API that this implements requires

[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=17501557#comment-17501557 ] Carter Kozak commented on LOG4J2-3424: -- Thank you for verifying, [~ggrzybek] :) > JDBC Appender

[jira] [Closed] (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:all-tabpanel ] Carter Kozak closed LOG4J2-3424. > JDBC Appender configuration properties not handled correctly after upgrading > to 2.17.2 >

[jira] [Resolved] (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:all-tabpanel ] Carter Kozak resolved LOG4J2-3424. -- Resolution: Fixed Merged into release-2.x, this will be included in 2.17.3 > JDBC Appender

[jira] [Assigned] (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:all-tabpanel ] Carter Kozak reassigned LOG4J2-3424: Assignee: Carter Kozak > JDBC Appender configuration properties not handled correctly

[jira] [Updated] (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:all-tabpanel ] Carter Kozak updated LOG4J2-3424: - Fix Version/s: 2.17.3 > JDBC Appender configuration properties not handled correctly after

[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=17501401#comment-17501401 ] Carter Kozak commented on LOG4J2-3424: -- That would be fantastic, my current PR is here:

[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=17501370#comment-17501370 ] Carter Kozak commented on LOG4J2-3424: -- [~ggrzybek] We have every intention of retaining backwards

[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=17501099#comment-17501099 ] Carter Kozak commented on LOG4J2-3424: -- Ouch, I see the cause, still looking into why this doesn't

[jira] [Work started] (LOG4J2-3404) Leak of DefaultConfiguration instances

[ https://issues.apache.org/jira/browse/LOG4J2-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3404 started by Carter Kozak. > Leak of DefaultConfiguration instances >

[jira] [Assigned] (LOG4J2-3404) Leak of DefaultConfiguration instances

[ https://issues.apache.org/jira/browse/LOG4J2-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3404: Assignee: Carter Kozak > Leak of DefaultConfiguration instances >

[jira] [Resolved] (LOG4J2-3404) Leak of DefaultConfiguration instances

[ https://issues.apache.org/jira/browse/LOG4J2-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3404. -- Resolution: Fixed > Leak of DefaultConfiguration instances >

[jira] [Resolved] (LOG4J2-3258) RollingFile fileName containing variables does not work on 2.17.0

[ https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3258. -- Resolution: Fixed > RollingFile fileName containing variables does not work on 2.17.0 >

[jira] [Commented] (LOG4J2-3258) RollingFile fileName containing variables does not work on 2.17.0

[ https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17494297#comment-17494297 ] Carter Kozak commented on LOG4J2-3258: -- Yes, this is resolved in 2.17.2-SNAPSHOT with the

[jira] [Assigned] (LOG4J2-3258) RollingFile fileName containing variables does not work on 2.17.0

[ https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3258: Assignee: Carter Kozak > RollingFile fileName containing variables does not work on

[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=17489558#comment-17489558 ] Carter Kozak commented on LOG4J2-3317: -- Test coverage is the best option. For what it's worth, I

[jira] [Closed] (LOG4J2-3382) ${ctx:mdcValue} no longer populating in Property tag

[ https://issues.apache.org/jira/browse/LOG4J2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3382. Resolution: Fixed The fix that I've committed shouldn't require any configuration changes like

[jira] [Resolved] (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:all-tabpanel ] Carter Kozak resolved LOG4J2-3317. -- Fix Version/s: 2.17.2 Resolution: Fixed Please test using a snapshot build, and close

[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=17489111#comment-17489111 ] Carter Kozak commented on LOG4J2-3317: -- This is fixed by

[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=17488202#comment-17488202 ] Carter Kozak commented on LOG4J2-3394: -- I'm sure we can come up with a reasonable path forward for

[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=17487505#comment-17487505 ] Carter Kozak commented on LOG4J2-3394: -- I see, the properties-specific configuration handling is

[jira] [Commented] (LOG4J2-3382) ${ctx:mdcValue} no longer populating in Property tag

[ https://issues.apache.org/jira/browse/LOG4J2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485333#comment-17485333 ] Carter Kozak commented on LOG4J2-3382: -- This PR addresses the ability to use properties within a

[jira] [Comment Edited] (LOG4J2-3382) ${ctx:mdcValue} no longer populating in Property tag

[ https://issues.apache.org/jira/browse/LOG4J2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484851#comment-17484851 ] Carter Kozak edited comment on LOG4J2-3382 at 1/31/22, 6:33 PM: Try

[jira] [Commented] (LOG4J2-3382) ${ctx:mdcValue} no longer populating in Property tag

[ https://issues.apache.org/jira/browse/LOG4J2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484851#comment-17484851 ] Carter Kozak commented on LOG4J2-3382: -- Try replacing $${ctx:txLogRecordType} with

[jira] [Assigned] (LOG4J2-3382) ${ctx:mdcValue} no longer populating in Property tag

[ https://issues.apache.org/jira/browse/LOG4J2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3382: Assignee: Carter Kozak > ${ctx:mdcValue} no longer populating in Property tag >

[jira] [Closed] (LOG4J2-3346) After 2.17.0 upgarde Route appenders with dynamic file writing are not working

[ https://issues.apache.org/jira/browse/LOG4J2-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3346. Resolution: Duplicate > After 2.17.0 upgarde Route appenders with dynamic file writing are not >

[jira] [Resolved] (LOG4J2-3333) Classloader deadlock in ThreadContextDataInjector

[ https://issues.apache.org/jira/browse/LOG4J2-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-. -- Resolution: Fixed I've resolved the issue on release-2.x for 2.17.2 – please verify from a

[jira] [Updated] (LOG4J2-3333) Classloader deadlock in ThreadContextDataInjector

[ https://issues.apache.org/jira/browse/LOG4J2-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-: - Fix Version/s: 2.17.2 > Classloader deadlock in ThreadContextDataInjector >

[jira] [Closed] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

[ https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3288. > Interpolator non-plugin codepath doesn't include all log4j-core lookups >

[jira] [Resolved] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

[ https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3288. -- Resolution: Fixed Closing via Commit 7ca3c4f5f206ca81dfdda2699703c9abc4d22624 in

[jira] [Updated] (LOG4J2-3358) 2.17.1: JsonLayout Context no longer working.

[ https://issues.apache.org/jira/browse/LOG4J2-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-3358: - Fix Version/s: 2.17.2 > 2.17.1: JsonLayout Context no longer working. >

[jira] [Updated] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

[ https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-3288: - Fix Version/s: 2.17.2 > Interpolator non-plugin codepath doesn't include all log4j-core lookups

[jira] [Commented] (LOG4J2-3358) 2.17.1: JsonLayout Context no longer working.

[ https://issues.apache.org/jira/browse/LOG4J2-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480313#comment-17480313 ] Carter Kozak commented on LOG4J2-3358: -- [~mduft] Please verify with a snapshot and close this

[jira] [Resolved] (LOG4J2-3358) 2.17.1: JsonLayout Context no longer working.

[ https://issues.apache.org/jira/browse/LOG4J2-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3358. -- Resolution: Fixed > 2.17.1: JsonLayout Context no longer working. >

[jira] [Commented] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

[ https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480303#comment-17480303 ] Carter Kozak commented on LOG4J2-3288: -- [~rgoers] I'd like to reintroduce the reverted behavior

[jira] [Assigned] (LOG4J2-3358) 2.17.1: JsonLayout Context no longer working.

[ https://issues.apache.org/jira/browse/LOG4J2-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3358: Assignee: Carter Kozak > 2.17.1: JsonLayout Context no longer working. >

[jira] [Assigned] (LOG4J2-3346) After 2.17.0 upgarde Route appenders with dynamic file writing are not working

[ https://issues.apache.org/jira/browse/LOG4J2-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3346: Assignee: Carter Kozak > After 2.17.0 upgarde Route appenders with dynamic file writing

[jira] [Assigned] (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:all-tabpanel ] Carter Kozak reassigned LOG4J2-3317: Assignee: Carter Kozak > After 2.17.1 upgarde, Route appenders with dynamic file writing

[jira] [Commented] (LOG4J2-3343) Add ability to use exclusion pattern filter on Map Resolver keys

[ https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478722#comment-17478722 ] Carter Kozak commented on LOG4J2-3343: -- I agree with Volkan here, I have a strong preference for

[jira] [Commented] (LOG4J2-3333) Classloader deadlock in ThreadContextDataInjector

[ https://issues.apache.org/jira/browse/LOG4J2-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478289#comment-17478289 ] Carter Kozak commented on LOG4J2-: -- Thanks, [~rschmitt]! I'm working on a patch here:

[jira] [Assigned] (LOG4J2-3333) Classloader deadlock in ThreadContextDataInjector

[ https://issues.apache.org/jira/browse/LOG4J2-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-: Assignee: Carter Kozak > Classloader deadlock in ThreadContextDataInjector >

[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=17478198#comment-17478198 ] Carter Kozak commented on LOG4J2-3317: -- Can you please provide the full contents of your

[jira] [Commented] (LOG4J2-3346) After 2.17.0 upgarde Route appenders with dynamic file writing are not working

[ https://issues.apache.org/jira/browse/LOG4J2-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478077#comment-17478077 ] Carter Kozak commented on LOG4J2-3346: -- Can you please provide the full contents of your

[jira] [Closed] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3345. > log4j-jpl must handle parameters as MessageFormat args >

[jira] [Updated] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-3345: - Fix Version/s: 2.17.2 > log4j-jpl must handle parameters as MessageFormat args >

[jira] [Resolved] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3345. -- Resolution: Fixed > log4j-jpl must handle parameters as MessageFormat args >

[jira] [Created] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

Carter Kozak created LOG4J2-3345: Summary: log4j-jpl must handle parameters as MessageFormat args Key: LOG4J2-3345 URL: https://issues.apache.org/jira/browse/LOG4J2-3345 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=17476415#comment-17476415 ] Carter Kozak commented on LOG4J2-3340: -- pr#700 looks like a great usability improvement :) >

[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=17476324#comment-17476324 ] Carter Kozak commented on LOG4J2-3340: -- I have the following in one of my

[jira] [Commented] (LOG4J2-3331) After upgrading version 2.13, the className and lineNumber cannot be obtained

[ https://issues.apache.org/jira/browse/LOG4J2-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474641#comment-17474641 ] Carter Kozak commented on LOG4J2-3331: -- Does your layout implement {{LocationAware}} and override

[jira] [Resolved] (LOG4J2-3282) log4j-to-jul JDK Logging Bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3282. -- Fix Version/s: 2.17.2 Resolution: Fixed > log4j-to-jul JDK Logging Bridge >

[jira] [Closed] (LOG4J2-3292) ExtendedLoggerWrapper.logMessage double-logs when location is requested

[ https://issues.apache.org/jira/browse/LOG4J2-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3292. > ExtendedLoggerWrapper.logMessage double-logs when location is requested >

[jira] [Resolved] (LOG4J2-3292) ExtendedLoggerWrapper.logMessage double-logs when location is requested

[ https://issues.apache.org/jira/browse/LOG4J2-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3292. -- Resolution: Fixed > ExtendedLoggerWrapper.logMessage double-logs when location is requested >

[jira] [Created] (LOG4J2-3292) ExtendedLoggerWrapper.logMessage double-logs when location is requested

Carter Kozak created LOG4J2-3292: Summary: ExtendedLoggerWrapper.logMessage double-logs when location is requested Key: LOG4J2-3292 URL: https://issues.apache.org/jira/browse/LOG4J2-3292 Project:

[jira] [Assigned] (LOG4J2-3289) log4j-to-slf4j should not re-format the result of Message.getFormattedMessage

[ https://issues.apache.org/jira/browse/LOG4J2-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3289: Assignee: Carter Kozak > log4j-to-slf4j should not re-format the result of

[jira] [Closed] (LOG4J2-3289) log4j-to-slf4j should not re-format the result of Message.getFormattedMessage

[ https://issues.apache.org/jira/browse/LOG4J2-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3289. > log4j-to-slf4j should not re-format the result of Message.getFormattedMessage >

[jira] [Resolved] (LOG4J2-3289) log4j-to-slf4j should not re-format the result of Message.getFormattedMessage

[ https://issues.apache.org/jira/browse/LOG4J2-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3289. -- Resolution: Fixed > log4j-to-slf4j should not re-format the result of

[jira] [Created] (LOG4J2-3289) log4j-to-slf4j should not re-format the result of Message.getFormattedMessage

Carter Kozak created LOG4J2-3289: Summary: log4j-to-slf4j should not re-format the result of Message.getFormattedMessage Key: LOG4J2-3289 URL: https://issues.apache.org/jira/browse/LOG4J2-3289

[jira] [Commented] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

[ https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465111#comment-17465111 ] Carter Kozak commented on LOG4J2-3288: -- There are several other places which use this path to

[jira] [Closed] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

[ https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3288. > Interpolator non-plugin codepath doesn't include all log4j-core lookups >

[jira] [Resolved] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

[ https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3288. -- Resolution: Fixed > Interpolator non-plugin codepath doesn't include all log4j-core lookups >

[jira] [Created] (LOG4J2-3288) Interpolator non-plugin codepath doesn't include all log4j-core lookups

Carter Kozak created LOG4J2-3288: Summary: Interpolator non-plugin codepath doesn't include all log4j-core lookups Key: LOG4J2-3288 URL: https://issues.apache.org/jira/browse/LOG4J2-3288 Project:

[jira] [Commented] (LOG4J2-3266) ${CTX :ThreadName} does not work

[ https://issues.apache.org/jira/browse/LOG4J2-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465056#comment-17465056 ] Carter Kozak commented on LOG4J2-3266: -- Not directly related to the reported problem, but you seem

[jira] [Comment Edited] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465052#comment-17465052 ] Carter Kozak edited comment on LOG4J2-3278 at 12/24/21, 4:34 PM: - I

[jira] [Commented] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465052#comment-17465052 ] Carter Kozak commented on LOG4J2-3278: -- I think this may actually be the same issue as

[jira] [Commented] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

[ https://issues.apache.org/jira/browse/LOG4J2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465049#comment-17465049 ] Carter Kozak commented on LOG4J2-3286: -- > _Isn't catching Throwable considered a bad practice?_ I

[jira] [Closed] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

[ https://issues.apache.org/jira/browse/LOG4J2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3286. Resolution: Information Provided Closing as information provided. If there's a bug, please don't

[jira] [Updated] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

[ https://issues.apache.org/jira/browse/LOG4J2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-3286: - Issue Type: Question (was: Bug) > 2.17 has reverted LOG4J-2972 fix in AppenderControl but

[jira] [Commented] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

[ https://issues.apache.org/jira/browse/LOG4J2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464765#comment-17464765 ] Carter Kozak commented on LOG4J2-3286: -- The AsyncAppender fix (and tests which verify it) are still

[jira] [Closed] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3284. Thanks for the contribution! > log4j-to-slf4j does not take the MessageFactory into account >

[jira] [Resolved] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3284. -- Resolution: Fixed > log4j-to-slf4j does not take the MessageFactory into account >

[jira] [Resolved] (LOG4J2-3264) MapLookup should lookup MapMessage before properties

[ https://issues.apache.org/jira/browse/LOG4J2-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3264. -- Fix Version/s: 2.17.1 Resolution: Fixed Please verify and close > MapLookup should

[jira] [Commented] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464714#comment-17464714 ] Carter Kozak commented on LOG4J2-3284: -- I don't believe this Jira configuration allows us to assign

[jira] [Created] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

Carter Kozak created LOG4J2-3284: Summary: log4j-to-slf4j does not take the MessageFactory into account Key: LOG4J2-3284 URL: https://issues.apache.org/jira/browse/LOG4J2-3284 Project: Log4j 2

[jira] [Assigned] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3284: Assignee: Carter Kozak > log4j-to-slf4j does not take the MessageFactory into account >

[jira] [Commented] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464709#comment-17464709 ] Carter Kozak commented on LOG4J2-3278: -- In 2.17.0 we limited recursive evaluation of lookups at

[jira] [Commented] (LOG4J2-3283) Add error-prone to build

[ https://issues.apache.org/jira/browse/LOG4J2-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464702#comment-17464702 ] Carter Kozak commented on LOG4J2-3283: -- Yes, several years ago I added it to the master branch, but

[jira] [Commented] (LOG4J2-3258) RollingFile fileName containing variables does not work on 2.17.0

[ https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464649#comment-17464649 ] Carter Kozak commented on LOG4J2-3258: -- I've added a document with some background context as well

[jira] [Closed] (LOG4J2-3270) Interpolator defaults should use only configuration properties

[ https://issues.apache.org/jira/browse/LOG4J2-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3270. > Interpolator defaults should use only configuration properties >

  1   2   3   4   5   6   7   >