[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like Camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430209#comment-15430209 ] Luca Burgazzoli commented on LOG4J2-905: In addition to this option, will you add

[jira] [Closed] (LOG4J2-1510) why MutableLogEvent don't keep original log object or even the ReusableObjectMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maple Wang closed LOG4J2-1510. -- Resolution: Fixed the suggestion works > why MutableLogEvent don't keep original log object or even th

[jira] [Created] (LOG4J2-1538) dynamic addition of filter may cause NPE

Igor Karpov created LOG4J2-1538: --- Summary: dynamic addition of filter may cause NPE Key: LOG4J2-1538 URL: https://issues.apache.org/jira/browse/LOG4J2-1538 Project: Log4j 2 Issue Type: Bug

[jira] [Updated] (LOG4J2-1538) dynamic addition of filter may cause NPE

[ https://issues.apache.org/jira/browse/LOG4J2-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Karpov updated LOG4J2-1538: Description: In my application, I need to add and remove a filter dynamically. The problem is, that

[jira] [Updated] (LOG4J2-1538) dynamic removal of filter may cause NPE

[ https://issues.apache.org/jira/browse/LOG4J2-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Karpov updated LOG4J2-1538: Summary: dynamic removal of filter may cause NPE (was: dynamic addition of filter may cause NPE)

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like Camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430613#comment-15430613 ] Ralph Goers commented on LOG4J2-905: We have no plans to do that as this should give y

Regression in ConfigurationScheduler

Hello, I am trying to test RollingFile/Policies/CronTriggeringPolicy with 2.6.2, but facing a strange behavior: ==> After first run it call rollover() every time. It looks there is a regression in the code according to https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;a=blobdiff;f=log

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430998#comment-15430998 ] Remko Popma commented on LOG4J2-1010: - I've modified DynamicThresholdFilter and Conte

[jira] [Updated] (LOG4J2-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1349: Attachment: DataStructOpsPerfMediumDataSet.png DataStructOpsPerfSmallDataSet.png

[jira] [Comment Edited] (LOG4J2-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431155#comment-15431155 ] Remko Popma edited comment on LOG4J2-1349 at 8/22/16 4:59 PM: -

[jira] [Commented] (LOG4J2-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431300#comment-15431300 ] Ralph Goers commented on LOG4J2-1349: - Hmmm. "now that LogEvents use ContextData..."

Re: ThreadContextMap2

Why doesn't ThreadContextMap2 extend ThreadContextMap? This feels highly unusual. Gary On Sat, Aug 20, 2016 at 5:10 PM, Gary Gregory wrote: > > On Aug 20, 2016 4:47 PM, "Remko Popma" wrote: > > > > Do you have anything specific in mind? > > Otherwise something may come out of my ongoing work f

[jira] [Commented] (LOG4J2-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431758#comment-15431758 ] Remko Popma commented on LOG4J2-1349: - Okay, I will add benchmarks for the "legacy in

[jira] [Created] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

Gary Gregory created LOG4J2-1539: Summary: Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit) Key: LOG4J2-1539 URL: https://issues.apache.org/jira/browse/LOG4J2-1539 Project: Log4j 2

[jira] [Updated] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1539: - Attachment: logging-log4j2.patch Patch. I plan on committing this soon. There is likely more inte

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431822#comment-15431822 ] Ralph Goers commented on LOG4J2-1539: - I dislike the patch because of the call to Log

Jenkins build became unstable: Log4j 2.x #2197

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Updated] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

[ https://issues.apache.org/jira/browse/LOG4J2-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1532: - Description: Don't throw an NPE from {{org.apache.logging.log4j.core.LoggerContext.setConfigurat

[jira] [Resolved] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

[ https://issues.apache.org/jira/browse/LOG4J2-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1532. -- Resolution: Fixed Assignee: Gary Gregory In Git master (with a slightly edited version of

[jira] [Updated] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

[ https://issues.apache.org/jira/browse/LOG4J2-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1532: - Fix Version/s: 2.7 > Don't throw an NPE from > org.apache.logging.log4j.core.LoggerContext.setCo

[jira] [Updated] (LOG4J2-1538) Dynamic removal of filter may cause NPE

[ https://issues.apache.org/jira/browse/LOG4J2-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1538: - Summary: Dynamic removal of filter may cause NPE (was: dynamic removal of filter may cause NPE)

[jira] [Resolved] (LOG4J2-1538) Dynamic removal of filter may cause NPE

[ https://issues.apache.org/jira/browse/LOG4J2-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1538. -- Resolution: Fixed Fix Version/s: 2.7 Igor, Thank you for your report and fix. This wa

Fwd: logging-log4j2 git commit: [LOG4J2-1538] Dynamic removal of filter may cause NPE.

What's actually amusing about this change is that the method is @PerformanceSensitive which to me means we should have cached the result of getFilter() anyways. ;) -- Forwarded message -- From: Date: 22 August 2016 at 19:24 Subject: logging-log4j2 git commit: [LOG4J2-1538] Dynamic

35 items in changes.xml since release 2.6.2 on July 5!

Wow, we've already accumulated 35 items in changes.xml since release 2.6.2 on July 5! I'm not sure if that is good or bad ;-) but we should think about what we want to complete for the next release. Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hi

Re: 35 items in changes.xml since release 2.6.2 on July 5!

I’m sure I have stuff I want to do. It just isn’t going to get done this week. The soonest I could target doing a release would be labor day weekend. But I expect I will probably spend most of that addressing issues I’ve been trying to get to. Ralph > On Aug 22, 2016, at 5:32 PM, Gary Gregory

[jira] [Updated] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

[ https://issues.apache.org/jira/browse/LOG4J2-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1532: - Description: Don't throw an NPE from {{org.apache.logging.log4j.core.LoggerContext.setConfigurat

[jira] [Updated] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1539: - Description: Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit): {code:java}

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431878#comment-15431878 ] Gary Gregory commented on LOG4J2-1539: -- Hi Ralph, Thank you for your review. I pla

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431879#comment-15431879 ] Gary Gregory commented on LOG4J2-1539: -- {quote} Actually, I dislike the currentConte

Re: 35 items in changes.xml since release 2.6.2 on July 5!

I'd like to finish the documentation for the AsyncAppender updates. I believe we also have a few outstanding branches now that could make it into 2.7. On 22 August 2016 at 19:39, Ralph Goers wrote: > I’m sure I have stuff I want to do. It just isn’t going to get done this > week. The soonest I c

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431898#comment-15431898 ] Ralph Goers commented on LOG4J2-1539: - As soon as you need the LoggerContext in the M

Jenkins build is back to stable : Log4j 2.x #2198

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Created] (LOG4J2-1540) The Core AbstractManager should track its LoggerContext

Gary Gregory created LOG4J2-1540: Summary: The Core AbstractManager should track its LoggerContext Key: LOG4J2-1540 URL: https://issues.apache.org/jira/browse/LOG4J2-1540 Project: Log4j 2 Iss

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431918#comment-15431918 ] Gary Gregory commented on LOG4J2-1539: -- I created [LOG4J2-1540] to track the LoggerC

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431923#comment-15431923 ] Ralph Goers commented on LOG4J2-1539: - Yes. As I said, I am afraid getContext() might

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431942#comment-15431942 ] Gary Gregory commented on LOG4J2-1539: -- OK, understood. Is there a type of change yo

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431954#comment-15431954 ] Gary Gregory commented on LOG4J2-1539: -- Hm... should the AbstractConfiguration hold

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431956#comment-15431956 ] Matt Sicker commented on LOG4J2-1539: - {{Builder}} is used by more than just plugin b

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431972#comment-15431972 ] Gary Gregory commented on LOG4J2-1539: -- OK, but my question is where does the Logger

[jira] [Comment Edited] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431956#comment-15431956 ] Matt Sicker edited comment on LOG4J2-1539 at 8/23/16 1:55 AM: -

[jira] [Commented] (LOG4J2-1539) Add Core API Configurator.shutdown(LoggerContext, long, TimeUnit)

[ https://issues.apache.org/jira/browse/LOG4J2-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431980#comment-15431980 ] Matt Sicker commented on LOG4J2-1539: - LoggerContext(s) is/are owned by the ContextSe

Jenkins build became unstable: Log4j 2.x #2199

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Created] (LOG4J2-1541) Fix file handle resource leak in XmlConfiguration.XmlConfiguration(ConfigurationSource)

Gary Gregory created LOG4J2-1541: Summary: Fix file handle resource leak in XmlConfiguration.XmlConfiguration(ConfigurationSource) Key: LOG4J2-1541 URL: https://issues.apache.org/jira/browse/LOG4J2-1541

Jenkins build is back to stable : Log4j 2.x #2200

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Jenkins build became unstable: Log4j 2.x #2201

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org