[jira] [Work started] (LOG4J2-2318) AsyncQueueFullMessageUtil causes unparsable message output

[ https://issues.apache.org/jira/browse/LOG4J2-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2318 started by Carter Kozak. > AsyncQueueFullMessageUtil causes unparsable message output > -

[jira] [Created] (LOG4J2-2318) AsyncQueueFullMessageUtil causes unparsable message output

Carter Kozak created LOG4J2-2318: Summary: AsyncQueueFullMessageUtil causes unparsable message output Key: LOG4J2-2318 URL: https://issues.apache.org/jira/browse/LOG4J2-2318 Project: Log4j 2

[jira] [Assigned] (LOG4J2-2318) AsyncQueueFullMessageUtil causes unparsable message output

[ https://issues.apache.org/jira/browse/LOG4J2-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2318: Assignee: Carter Kozak > AsyncQueueFullMessageUtil causes unparsable message output >

[jira] [Resolved] (LOG4J2-2317) getNonNullImmutableMessage should retain format and parameters

[ https://issues.apache.org/jira/browse/LOG4J2-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2317. -- Resolution: Fixed Fixed via 9a07b5a4ac1a8edb9a2be6bd472f19ba6804e4fd > getNonNullImmutableMess

[jira] [Closed] (LOG4J2-2317) getNonNullImmutableMessage should retain format and parameters

[ https://issues.apache.org/jira/browse/LOG4J2-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2317. > getNonNullImmutableMessage should retain format and parameters >

[jira] [Assigned] (LOG4J2-2317) getNonNullImmutableMessage should retain format and parameters

[ https://issues.apache.org/jira/browse/LOG4J2-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2317: Assignee: Carter Kozak > getNonNullImmutableMessage should retain format and parameters >

[jira] [Created] (LOG4J2-2317) getNonNullImmutableMessage should retain format and parameters

Carter Kozak created LOG4J2-2317: Summary: getNonNullImmutableMessage should retain format and parameters Key: LOG4J2-2317 URL: https://issues.apache.org/jira/browse/LOG4J2-2317 Project: Log4j 2

[jira] [Commented] (LOG4J2-2269) Memory leaking of replacement parameters in case of enableThreadlocals=true

[ https://issues.apache.org/jira/browse/LOG4J2-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438213#comment-16438213 ] Carter Kozak commented on LOG4J2-2269: -- I wonder if something along these lines woul

[jira] [Commented] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436635#comment-16436635 ] Carter Kozak commented on LOG4J2-2301: -- Not a problem, I'm not in a rush. Thanks! >

[jira] [Work started] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2301 started by Carter Kozak. > gc-free mixed async loging loses parameter values after the first appender > -

[jira] [Commented] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434795#comment-16434795 ] Carter Kozak commented on LOG4J2-2301: -- Alright, I've refactored AsyncLoggerConfig a

[jira] [Closed] (LOG4J2-2299) Using "asyncLogger" with AsyncLoggerContextSelector loses some event data

[ https://issues.apache.org/jira/browse/LOG4J2-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2299. Resolution: Duplicate Fix Version/s: 3.0.0 LOG4J2-2307 improved message mementos, fixing the

[jira] [Resolved] (LOG4J2-2032) Curly braces in parameters are treated as placeholders

[ https://issues.apache.org/jira/browse/LOG4J2-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2032. -- Resolution: Fixed Fix Version/s: 3.0.0 Resolved with the fix for LOG4J2-2118. > Curly b

[jira] [Assigned] (LOG4J2-2032) Curly braces in parameters are treated as placeholders

[ https://issues.apache.org/jira/browse/LOG4J2-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2032: Assignee: Carter Kozak > Curly braces in parameters are treated as placeholders >

[jira] [Assigned] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2301: Assignee: Carter Kozak > gc-free mixed async loging loses parameter values after the first

[jira] [Closed] (LOG4J2-2127) Remove unnecessary threadlocal in MdcPatternConverter

[ https://issues.apache.org/jira/browse/LOG4J2-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2127. > Remove unnecessary threadlocal in MdcPatternConverter > -

[jira] [Resolved] (LOG4J2-2307) Reusable event memento messages should retain format

[ https://issues.apache.org/jira/browse/LOG4J2-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2307. -- Resolution: Fixed > Reusable event memento messages should retain format >

[jira] [Closed] (LOG4J2-2307) Reusable event memento messages should retain format

[ https://issues.apache.org/jira/browse/LOG4J2-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2307. > Reusable event memento messages should retain format > --

[jira] [Work started] (LOG4J2-2307) Reusable event memento messages should retain format

[ https://issues.apache.org/jira/browse/LOG4J2-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2307 started by Carter Kozak. > Reusable event memento messages should retain format > ---

[jira] [Created] (LOG4J2-2307) Reusable event memento messages should retain format

Carter Kozak created LOG4J2-2307: Summary: Reusable event memento messages should retain format Key: LOG4J2-2307 URL: https://issues.apache.org/jira/browse/LOG4J2-2307 Project: Log4j 2 Issue

[jira] [Closed] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

[ https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2306. > Investigate using Error Prone for Static Analysis > -

[jira] [Resolved] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

[ https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2306. -- Resolution: Fixed Fix Version/s: 3.0.0 > Investigate using Error Prone for Static Analys

[jira] [Commented] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

[ https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426141#comment-16426141 ] Carter Kozak commented on LOG4J2-2306: -- Commit with error prone enabled as well as b

[jira] [Assigned] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

[ https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2306: Assignee: Carter Kozak > Investigate using Error Prone for Static Analysis > -

[jira] [Created] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

Carter Kozak created LOG4J2-2306: Summary: Investigate using Error Prone for Static Analysis Key: LOG4J2-2306 URL: https://issues.apache.org/jira/browse/LOG4J2-2306 Project: Log4j 2 Issue Typ

[jira] [Closed] (LOG4J2-2036) CompositeConfiguration with monitorInterval fails to reload full configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2036. > CompositeConfiguration with monitorInterval fails to reload full configuration >

[jira] [Resolved] (LOG4J2-2036) CompositeConfiguration with monitorInterval fails to reload full configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2036. -- Resolution: Cannot Reproduce I'm unable to reproduce this issue again using 2.11.0, closing it

[jira] [Commented] (LOG4J2-2299) Using "asyncLogger" with AsyncLoggerContextSelector loses some event data

[ https://issues.apache.org/jira/browse/LOG4J2-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423451#comment-16423451 ] Carter Kozak commented on LOG4J2-2299: -- Implementation of the proposal for the memen

[jira] [Comment Edited] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423340#comment-16423340 ] Carter Kozak edited comment on LOG4J2-2301 at 4/3/18 3:48 AM: -

[jira] [Commented] (LOG4J2-2299) Using "asyncLogger" with AsyncLoggerContextSelector loses some event data

[ https://issues.apache.org/jira/browse/LOG4J2-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423408#comment-16423408 ] Carter Kozak commented on LOG4J2-2299: -- My initial change is here: [https://github.

[jira] [Commented] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423340#comment-16423340 ] Carter Kozak commented on LOG4J2-2301: -- Perfect, will do! > gc-free mixed async log

[jira] [Created] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

Carter Kozak created LOG4J2-2301: Summary: gc-free mixed async loging loses parameter values after the first appender Key: LOG4J2-2301 URL: https://issues.apache.org/jira/browse/LOG4J2-2301 Project: L

[jira] [Work started] (LOG4J2-2299) Using "asyncLogger" with AsyncLoggerContextSelector loses some event data

[ https://issues.apache.org/jira/browse/LOG4J2-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2299 started by Carter Kozak. > Using "asyncLogger" with AsyncLoggerContextSelector loses some event data > --

[jira] [Assigned] (LOG4J2-2299) Using "asyncLogger" with AsyncLoggerContextSelector loses some event data

[ https://issues.apache.org/jira/browse/LOG4J2-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2299: Assignee: Carter Kozak > Using "asyncLogger" with AsyncLoggerContextSelector loses some ev

[jira] [Commented] (LOG4J2-2299) Using "asyncLogger" with AsyncLoggerContextSelector loses some event data

[ https://issues.apache.org/jira/browse/LOG4J2-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420937#comment-16420937 ] Carter Kozak commented on LOG4J2-2299: -- I'd like to self-assign this issue, but I do

<    2   3   4   5   6   7