[jira] [Commented] (LOG4J2-2341) JsonLayout not working with AsyncLoggerContextSelector in 2.11.0

2019-03-23 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799756#comment-16799756 ] Carter Kozak commented on LOG4J2-2341: -- > That interface is documented as not being

[jira] [Commented] (LOG4J2-2341) JsonLayout not working with AsyncLoggerContextSelector in 2.11.0

2019-03-20 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797818#comment-16797818 ] Carter Kozak commented on LOG4J2-2341: -- Something along these lines should do what

[jira] [Commented] (LOG4J2-2341) JsonLayout not working with AsyncLoggerContextSelector in 2.11.0

2019-03-20 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797808#comment-16797808 ] Carter Kozak commented on LOG4J2-2341: -- Yep, looking at the implementation that mak

[jira] [Commented] (LOG4J2-2341) JsonLayout not working with AsyncLoggerContextSelector in 2.11.0

2019-03-20 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797695#comment-16797695 ] Carter Kozak commented on LOG4J2-2341: -- You beat me to it! I can take a look at a m

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

2019-02-05 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761156#comment-16761156 ] Carter Kozak commented on LOG4J2-2269: -- The problem is that after a MutableLogEvent

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

2019-02-05 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761128#comment-16761128 ] Carter Kozak commented on LOG4J2-2269: -- Are you sure that you're accessing the even

[jira] [Closed] (LOG4J2-2545) RoutingAppender.Builder.setPurgePolicy should return the builder

2019-02-04 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2545. > RoutingAppender.Builder.setPurgePolicy should return the builder > -

[jira] [Assigned] (LOG4J2-2545) RoutingAppender.Builder.setPurgePolicy should return the builder

2019-02-04 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2545: Assignee: Carter Kozak > RoutingAppender.Builder.setPurgePolicy should return the builder

[jira] [Resolved] (LOG4J2-2545) RoutingAppender.Builder.setPurgePolicy should return the builder

2019-02-04 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2545. -- Resolution: Fixed Fix Version/s: 3.0.0 Fixed on master, holding off on release-2.x whil

[jira] [Updated] (LOG4J2-2545) RoutingAppender.Builder.setPurgePolicy should return the builder

2019-02-04 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2545: - Summary: RoutingAppender.Builder.setPurgePolicy should return the builder (was: RoutingAppender

[jira] [Created] (LOG4J2-2545) RoutingAppender.BuilderlsetPurgePolichy should return the builder

2019-02-04 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2545: Summary: RoutingAppender.BuilderlsetPurgePolichy should return the builder Key: LOG4J2-2545 URL: https://issues.apache.org/jira/browse/LOG4J2-2545 Project: Log4j 2

[jira] [Closed] (LOG4J2-2533) Garbage creation introduced by LOG4J2-2301

2019-01-14 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2533. Closing as the reporter has verified the patch already. > Garbage creation introduced by LOG4J2-2301

[jira] [Resolved] (LOG4J2-2533) Garbage creation introduced by LOG4J2-2301

2019-01-14 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2533. -- Resolution: Fixed > Garbage creation introduced by LOG4J2-2301 > -

[jira] [Updated] (LOG4J2-2533) Garbage creation introduced by LOG4J2-2301

2019-01-14 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2533: - Description: Reported here: [https://github.com/apache/logging-log4j2/pull/251] {noformat} Stack

[jira] [Created] (LOG4J2-2533) Garbage creation introduced by LOG4J2-2301

2019-01-14 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2533: Summary: Garbage creation introduced by LOG4J2-2301 Key: LOG4J2-2533 URL: https://issues.apache.org/jira/browse/LOG4J2-2533 Project: Log4j 2 Issue Type: Impr

[jira] [Closed] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-13 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2530. Closing out based on the PR conversation, the new unit tests (thanks!) are sufficient verification.

[jira] [Commented] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-13 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741728#comment-16741728 ] Carter Kozak commented on LOG4J2-2530: -- Thank you for your contribution [~tspencer]

[jira] [Resolved] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-13 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2530. -- Resolution: Fixed > StructuredDataMessage is not logged > ---

[jira] [Assigned] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-13 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2530: Assignee: Carter Kozak > StructuredDataMessage is not logged > --

[jira] [Updated] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-13 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2530: - Fix Version/s: 3.0.0 > StructuredDataMessage is not logged > ---

[jira] [Commented] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-10 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739559#comment-16739559 ] Carter Kozak commented on LOG4J2-2530: -- Not at all, your input on my poor implement

[jira] [Commented] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-10 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739521#comment-16739521 ] Carter Kozak commented on LOG4J2-2530: -- Thanks [~tspencer]! I've pushed a potential

[jira] [Commented] (LOG4J2-2530) StructuredDataMessage is not logged

2019-01-10 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739525#comment-16739525 ] Carter Kozak commented on LOG4J2-2530: -- The MapLookup break has already been fixed

[jira] [Commented] (LOG4J2-2490) thread blocked when logging numerous exception stack

2019-01-03 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733262#comment-16733262 ] Carter Kozak commented on LOG4J2-2490: -- I'd want to handle eviction, otherwise shar

[jira] [Commented] (LOG4J2-2506) MutableLogEvent references to other objects are cleared after each use

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732164#comment-16732164 ] Carter Kozak commented on LOG4J2-2506: -- I'm not sure if we can consider this a regr

[jira] [Assigned] (LOG4J2-2522) Make MapMessageLookup.lookup usable with MapMessage again

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2522: Assignee: Carter Kozak > Make MapMessageLookup.lookup usable with MapMessage again >

[jira] [Resolved] (LOG4J2-2522) Make MapMessageLookup.lookup usable with MapMessage again

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2522. -- Resolution: Fixed > Make MapMessageLookup.lookup usable with MapMessage again > --

[jira] [Work started] (LOG4J2-2522) Make MapMessageLookup.lookup usable with MapMessage again

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2522 started by Carter Kozak. > Make MapMessageLookup.lookup usable with MapMessage again > -

[jira] [Updated] (LOG4J2-2522) Make MapMessageLookup.lookup usable with MapMessage again

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2522: - Fix Version/s: 2.11.2 3.0.0 > Make MapMessageLookup.lookup usable with MapMes

[jira] [Commented] (LOG4J2-2522) Make MapMessageLookup.lookup usable with MapMessage again

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732138#comment-16732138 ] Carter Kozak commented on LOG4J2-2522: -- Thanks for your contribution [~lesiak]! I'v

[jira] [Commented] (LOG4J2-2506) MutableLogEvent references to other objects are cleared after each use

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732111#comment-16732111 ] Carter Kozak commented on LOG4J2-2506: -- I'm a bit worried about this usage of Mutab

[jira] [Commented] (LOG4J2-2490) thread blocked when logging numerous exception stack

2019-01-02 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732082#comment-16732082 ] Carter Kozak commented on LOG4J2-2490: -- More information on this ticket: https://is

[jira] [Resolved] (LOG4J2-2527) concurrent modification exception when using list appender

2018-12-30 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2527. -- Resolution: Fixed The fix has merged to the release-2.x and master branches > concurrent modi

[jira] [Closed] (LOG4J2-2527) concurrent modification exception when using list appender

2018-12-30 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2527. > concurrent modification exception when using list appender > ---

[jira] [Updated] (LOG4J2-2527) concurrent modification exception when using list appender

2018-12-30 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2527: - Fix Version/s: 2.11.2 3.0.0 > concurrent modification exception when using li

[jira] [Assigned] (LOG4J2-2527) concurrent modification exception when using list appender

2018-12-30 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2527: Assignee: Carter Kozak > concurrent modification exception when using list appender > ---

[jira] [Commented] (LOG4J2-2527) concurrent modification exception when using list appender

2018-12-30 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730993#comment-16730993 ] Carter Kozak commented on LOG4J2-2527: -- Thank you for the report, I agree that this

[jira] [Commented] (LOG4J2-1137) Allow events to be buffered until something triggers and causes them to be logged.

2018-11-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677080#comment-16677080 ] Carter Kozak commented on LOG4J2-1137: -- We would need to be careful about buffering

[jira] [Created] (LOG4J2-2498) Replace functional interfaces with java8 java.util

2018-11-05 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2498: Summary: Replace functional interfaces with java8 java.util Key: LOG4J2-2498 URL: https://issues.apache.org/jira/browse/LOG4J2-2498 Project: Log4j 2 Issue Ty

[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-10-30 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668846#comment-16668846 ] Carter Kozak commented on LOG4J2-2391: -- Thank you for the detailed post [~fliaping]

[jira] [Closed] (LOG4J2-2478) JMH Benchmarks in not consuming all computed variables (risk of DCE)

2018-10-16 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2478. Resolution: Fixed > JMH Benchmarks in not consuming all computed variables (risk of DCE) > ---

[jira] [Commented] (LOG4J2-2478) JMH Benchmarks in not consuming all computed variables (risk of DCE)

2018-10-16 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652679#comment-16652679 ] Carter Kozak commented on LOG4J2-2478: -- Merged to master and release-2.x, Thank you

[jira] [Commented] (LOG4J2-2475) Limit reusable event.clear parameter clearing to argsCount

2018-10-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646532#comment-16646532 ] Carter Kozak commented on LOG4J2-2475: -- I don't believe so – we can limit the clear

[jira] [Created] (LOG4J2-2475) Limit reusable event.clear parameter clearing to argsCount

2018-10-11 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2475: Summary: Limit reusable event.clear parameter clearing to argsCount Key: LOG4J2-2475 URL: https://issues.apache.org/jira/browse/LOG4J2-2475 Project: Log4j 2

[jira] [Closed] (LOG4J2-2444) ErrorHandler should be invoked with the failing LogEvent when possible

2018-09-12 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2444. > ErrorHandler should be invoked with the failing LogEvent when possible > ---

[jira] [Resolved] (LOG4J2-2444) ErrorHandler should be invoked with the failing LogEvent when possible

2018-09-12 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2444. -- Resolution: Fixed > ErrorHandler should be invoked with the failing LogEvent when possible > -

[jira] [Updated] (LOG4J2-2444) ErrorHandler should be invoked with the failing LogEvent when possible

2018-09-12 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2444: - Fix Version/s: 2.11.1 3.0.0 > ErrorHandler should be invoked with the failing

[jira] [Assigned] (LOG4J2-2444) ErrorHandler should be invoked with the failing LogEvent when possible

2018-09-12 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2444: Assignee: Carter Kozak > ErrorHandler should be invoked with the failing LogEvent when po

[jira] [Created] (LOG4J2-2444) ErrorHandler should be invoked with the failing LogEvent when possible

2018-09-12 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2444: Summary: ErrorHandler should be invoked with the failing LogEvent when possible Key: LOG4J2-2444 URL: https://issues.apache.org/jira/browse/LOG4J2-2444 Project: Log4j

[jira] [Resolved] (LOG4J2-2441) AbstractAppender.setHandler(null) should not set a null ErrorHandler

2018-09-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2441. -- Resolution: Fixed > AbstractAppender.setHandler(null) should not set a null ErrorHandler > ---

[jira] [Closed] (LOG4J2-2441) AbstractAppender.setHandler(null) should not set a null ErrorHandler

2018-09-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2441. > AbstractAppender.setHandler(null) should not set a null ErrorHandler > -

[jira] [Updated] (LOG4J2-2441) AbstractAppender.setHandler(null) should not set a null ErrorHandler

2018-09-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2441: - Fix Version/s: 2.11.2 3.0.0 > AbstractAppender.setHandler(null) should not se

[jira] [Created] (LOG4J2-2441) AbstractAppender.setHandler(null) should not set a null ErrorHandler

2018-09-11 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2441: Summary: AbstractAppender.setHandler(null) should not set a null ErrorHandler Key: LOG4J2-2441 URL: https://issues.apache.org/jira/browse/LOG4J2-2441 Project: Log4j 2

[jira] [Updated] (LOG4J2-2441) AbstractAppender.setHandler(null) should not set a null ErrorHandler

2018-09-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2441: - Affects Version/s: 3.0.0 2.11.1 > AbstractAppender.setHandler(null) shoul

[jira] [Updated] (LOG4J2-2423) Rolled files are not deleted when a date is used in the pattern

2018-08-28 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2423: - Description: In my appender definition I set filePattern="app/log/trace.%d\{-MM-dd}-%i.log.

[jira] [Updated] (LOG4J2-2423) Rolled files are not deleted when a date is used in the pattern

2018-08-28 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2423: - Description: In my appender definition I set filePattern="app/log/trace.%d\{-MM-dd}-%i.log.

[jira] [Created] (LOG4J2-2423) Rolled files are not deleted when a date is used in the pattern

2018-08-28 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2423: Summary: Rolled files are not deleted when a date is used in the pattern Key: LOG4J2-2423 URL: https://issues.apache.org/jira/browse/LOG4J2-2423 Project: Log4j 2

[jira] [Assigned] (LOG4J2-2423) Rolled files are not deleted when a date is used in the pattern

2018-08-28 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2423: Assignee: Carter Kozak > Rolled files are not deleted when a date is used in the pattern

[jira] [Assigned] (LOG4J2-2409) Mixed async loggers should not fully initialize ThrowableProxy unless it is used

2018-08-14 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2409: Assignee: Carter Kozak > Mixed async loggers should not fully initialize ThrowableProxy u

[jira] [Created] (LOG4J2-2409) Mixed async loggers should not fully initialize ThrowableProxy unless it is used

2018-08-14 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2409: Summary: Mixed async loggers should not fully initialize ThrowableProxy unless it is used Key: LOG4J2-2409 URL: https://issues.apache.org/jira/browse/LOG4J2-2409 Proj

[jira] [Closed] (LOG4J2-2408) AsyncLoggerContextSelector with ThrowableProxy uses incorrect CCL

2018-08-14 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2408. Resolution: Duplicate oops, too many tabs > AsyncLoggerContextSelector with ThrowableProxy uses i

[jira] [Created] (LOG4J2-2408) AsyncLoggerContextSelector with ThrowableProxy uses incorrect CCL

2018-08-14 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2408: Summary: AsyncLoggerContextSelector with ThrowableProxy uses incorrect CCL Key: LOG4J2-2408 URL: https://issues.apache.org/jira/browse/LOG4J2-2408 Project: Log4j 2

[jira] [Created] (LOG4J2-2407) AsyncLoggerContextSelector with ThrowableProxy uses incorrect CCL

2018-08-14 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2407: Summary: AsyncLoggerContextSelector with ThrowableProxy uses incorrect CCL Key: LOG4J2-2407 URL: https://issues.apache.org/jira/browse/LOG4J2-2407 Project: Log4j 2

[jira] [Assigned] (LOG4J2-2407) AsyncLoggerContextSelector with ThrowableProxy uses incorrect CCL

2018-08-14 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2407: Assignee: Carter Kozak > AsyncLoggerContextSelector with ThrowableProxy uses incorrect CC

[jira] [Commented] (LOG4J2-2399) Reusable Messages do not respect log4j.format.msg.async

2018-08-08 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574054#comment-16574054 ] Carter Kozak commented on LOG4J2-2399: -- Absolutely, I'll put together some concrete

[jira] [Updated] (LOG4J2-2363) ReusableObjectMessage does not pass object parameter to reusable events

2018-08-08 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2363: - Fix Version/s: 2.11.2 > ReusableObjectMessage does not pass object parameter to reusable events

[jira] [Updated] (LOG4J2-2363) ReusableObjectMessage does not pass object parameter to reusable events

2018-08-08 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2363: - Affects Version/s: 2.11.1 > ReusableObjectMessage does not pass object parameter to reusable eve

[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-08-07 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572365#comment-16572365 ] Carter Kozak commented on LOG4J2-2391: -- The one I pushed to the gh mirror improved

[jira] [Created] (LOG4J2-2399) Reusable Messages do not respect log4j.format.msg.async

2018-08-07 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2399: Summary: Reusable Messages do not respect log4j.format.msg.async Key: LOG4J2-2399 URL: https://issues.apache.org/jira/browse/LOG4J2-2399 Project: Log4j 2 Iss

[jira] [Assigned] (LOG4J2-2399) Reusable Messages do not respect log4j.format.msg.async

2018-08-07 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2399: Assignee: Carter Kozak > Reusable Messages do not respect log4j.format.msg.async > --

[jira] [Updated] (LOG4J2-2348) MongoDB Test Flakes

2018-08-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2348: - Fix Version/s: 2.11.2 3.0.0 > MongoDB Test Flakes > --- > >

[jira] [Resolved] (LOG4J2-2348) MongoDB Test Flakes

2018-08-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2348. -- Resolution: Fixed > MongoDB Test Flakes > --- > > Key: LOG4J2-

[jira] [Resolved] (LOG4J2-2201) ReusableParametrizedMessages keeps references to objects beyond their expected lifetime

2018-08-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2201. -- Resolution: Fixed I've merged a fix to master and release-2.x, though the issue fixed by this

[jira] [Updated] (LOG4J2-2201) ReusableParametrizedMessages keeps references to objects beyond their expected lifetime

2018-08-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2201: - Fix Version/s: 2.11.2 3.0.0 > ReusableParametrizedMessages keeps references t

[jira] [Commented] (LOG4J2-2242) Log4j2 - logger overrides another logger's message

2018-08-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570767#comment-16570767 ] Carter Kozak commented on LOG4J2-2242: -- [~borek] I think this was fixed in 2.11.1 w

[jira] [Assigned] (LOG4J2-2201) ReusableParametrizedMessages keeps references to objects beyond their expected lifetime

2018-08-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2201: Assignee: Carter Kozak > ReusableParametrizedMessages keeps references to objects beyond

[jira] [Commented] (LOG4J2-2201) ReusableParametrizedMessages keeps references to objects beyond their expected lifetime

2018-08-06 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570757#comment-16570757 ] Carter Kozak commented on LOG4J2-2201: -- I think this is fixed in 2.11.1 by LOG4J2-2

[jira] [Updated] (LOG4J2-2365) NameAbbreviator skips first fragments

2018-08-03 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2365: - Fix Version/s: 2.11.2 3.0.0 > NameAbbreviator skips first fragments > ---

[jira] [Resolved] (LOG4J2-2365) NameAbbreviator skips first fragments

2018-08-03 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2365. -- Resolution: Fixed Apologies for the delay [~undefz]. Thank you for your contribution, I applie

[jira] [Assigned] (LOG4J2-2365) NameAbbreviator skips first fragments

2018-08-03 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2365: Assignee: Carter Kozak > NameAbbreviator skips first fragments >

[jira] [Updated] (LOG4J2-2365) NameAbbreviator skips first fragments

2018-08-03 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2365: - Affects Version/s: 2.11.1 > NameAbbreviator skips first fragments >

[jira] [Commented] (LOG4J2-2398) RandomAccessFileManager default buffer size shoule be configurable

2018-08-01 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566202#comment-16566202 ] Carter Kozak commented on LOG4J2-2398: -- That makes sense, thanks. Appender templati

[jira] [Closed] (LOG4J2-2398) RandomAccessFileManager default buffer size shoule be configurable

2018-08-01 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2398. Resolution: Won't Fix > RandomAccessFileManager default buffer size shoule be configurable > -

[jira] [Commented] (LOG4J2-2398) RandomAccessFileManager default buffer size shoule be configurable

2018-08-01 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566157#comment-16566157 ] Carter Kozak commented on LOG4J2-2398: -- It can, however I would like to configure t

[jira] [Created] (LOG4J2-2398) RandomAccessFileManager default buffer size shoule be configurable

2018-08-01 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2398: Summary: RandomAccessFileManager default buffer size shoule be configurable Key: LOG4J2-2398 URL: https://issues.apache.org/jira/browse/LOG4J2-2398 Project: Log4j 2

[jira] [Assigned] (LOG4J2-2398) RandomAccessFileManager default buffer size shoule be configurable

2018-08-01 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2398: Assignee: Carter Kozak > RandomAccessFileManager default buffer size shoule be configurab

[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-07-27 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559907#comment-16559907 ] Carter Kozak commented on LOG4J2-2391: -- [~ralph.go...@dslextreme.com] Not yet, I wi

[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-07-27 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559879#comment-16559879 ] Carter Kozak commented on LOG4J2-2391: -- Thanks [~rem...@yahoo.com]! I'm going to ke

[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-07-26 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559169#comment-16559169 ] Carter Kozak commented on LOG4J2-2391: -- Getting closer! In a refactor, this initia

[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-07-24 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554999#comment-16554999 ] Carter Kozak commented on LOG4J2-2391: -- Second commit pushed to that github PR prov

[jira] [Assigned] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-07-23 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2391: Assignee: Carter Kozak > Investigate ThrowableProxy performance > ---

[jira] [Created] (LOG4J2-2391) Investigate ThrowableProxy performance

2018-07-23 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2391: Summary: Investigate ThrowableProxy performance Key: LOG4J2-2391 URL: https://issues.apache.org/jira/browse/LOG4J2-2391 Project: Log4j 2 Issue Type: Task

[jira] [Resolved] (LOG4J2-2376) StringBuilders.escapeXml should run in linear time

2018-07-16 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2376. -- Resolution: Fixed Running locally the StringBuilderEscapeBenchmark.escapeXmlLargeString P50 ti

[jira] [Closed] (LOG4J2-2376) StringBuilders.escapeXml should run in linear time

2018-07-16 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2376. > StringBuilders.escapeXml should run in linear time > ---

[jira] [Created] (LOG4J2-2376) StringBuilders.escapeXml should run in linear time

2018-07-16 Thread Carter Kozak (JIRA)
Carter Kozak created LOG4J2-2376: Summary: StringBuilders.escapeXml should run in linear time Key: LOG4J2-2376 URL: https://issues.apache.org/jira/browse/LOG4J2-2376 Project: Log4j 2 Issue Ty

[jira] [Assigned] (LOG4J2-2376) StringBuilders.escapeXml should run in linear time

2018-07-16 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2376: Assignee: Carter Kozak > StringBuilders.escapeXml should run in linear time > ---

[jira] [Commented] (LOG4J2-2376) StringBuilders.escapeXml should run in linear time

2018-07-16 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545531#comment-16545531 ] Carter Kozak commented on LOG4J2-2376: -- Proposed fix from github: https://github.co

[jira] [Resolved] (LOG4J2-2373) StringBuilder escapeJson performs unnecessary Memory Allocations

2018-07-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2373. -- Resolution: Fixed Thanks for your contribution [~kmeurer]! > StringBuilder escapeJson perform

[jira] [Closed] (LOG4J2-2373) StringBuilder escapeJson performs unnecessary Memory Allocations

2018-07-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2373. > StringBuilder escapeJson performs unnecessary Memory Allocations > -

[jira] [Updated] (LOG4J2-2373) StringBuilder escapeJson performs unnecessary Memory Allocations

2018-07-11 Thread Carter Kozak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2373: - Affects Version/s: 2.11.0 > StringBuilder escapeJson performs unnecessary Memory Allocations > -

<    1   2   3   4   5   6   7   >