[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186686#comment-15186686 ] Remko Popma commented on LOG4J2-1116: - Not sure. AppenderControl carefully nulls out

[jira] [Commented] (LOG4J2-1133) In page "Configuration", section "Property Substitution", add "jndi" context

[ https://issues.apache.org/jira/browse/LOG4J2-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186566#comment-15186566 ] Fabien Baligand commented on LOG4J2-1133: - Ok. Do you know when 2.6 will be rele

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186548#comment-15186548 ] Ralph Goers commented on LOG4J2-1116: - Well AppenderControl, DatePatternConverter, Pa

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186539#comment-15186539 ] Remko Popma commented on LOG4J2-1116: - I experimented with making ThreadLocal fields

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186536#comment-15186536 ] Remko Popma commented on LOG4J2-1116: - ThreadLocals containing JDK classes (StringBui

[jira] [Comment Edited] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186503#comment-15186503 ] Ralph Goers edited comment on LOG4J2-1116 at 3/9/16 5:10 AM: -

[jira] [Comment Edited] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186503#comment-15186503 ] Ralph Goers edited comment on LOG4J2-1116 at 3/9/16 5:04 AM: -

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186503#comment-15186503 ] Ralph Goers commented on LOG4J2-1116: - My understanding is that this problem only exi

Re: Fast and Furious

ThreadLocals containing JDK classes (StringBuilder, etc) are not a problem. Their classloader is the system classloader, not the web app classloader, so these ThreadLocals do not have a reference to the web app classes and do not prevent web app classes from being garbage collected. This idiom is

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186475#comment-15186475 ] Remko Popma commented on LOG4J2-1116: - If each web-app has its own copy of the log4j

Re: Fast and Furious

I still am unclear as to why you are thinking GC-free mode won’t work in web apps. What is the issue with ThreadLocals that causes the problem? We are using ThreadLocals for other things that seem to be working. Ralph > On Mar 8, 2016, at 3:05 PM, Remko Popma wrote: > > Some of the recent c

Re: Fast and Furious

Maybe we can all meet at some tropical island in the middle! Ralph > On Mar 8, 2016, at 4:43 PM, Remko Popma wrote: > > Would be fun to meet in person at some point though... > > On Wed, Mar 9, 2016 at 10:27 AM, Remko Popma > wrote: > No, I'm in Sydney. > > On W

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186161#comment-15186161 ] Ralph Goers commented on LOG4J2-1116: - Now I am really confused. If each web-app has

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186156#comment-15186156 ] Ralph Goers commented on LOG4J2-1116: - I am a little confused about the issue with Th

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186092#comment-15186092 ] Remko Popma commented on LOG4J2-1116: - I haven't tested but that might solve the prob

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

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

Re: Fast and Furious

+1 :-) On Mar 8, 2016 3:44 PM, "Remko Popma" wrote: > Would be fun to meet in person at some point though... > > On Wed, Mar 9, 2016 at 10:27 AM, Remko Popma > wrote: > >> No, I'm in Sydney. >> >> On Wed, Mar 9, 2016 at 9:41 AM, Gary Gregory >> wrote: >> >>> Are you in SoCal perchance? >>> >>>

Re: Fast and Furious

Would be fun to meet in person at some point though... On Wed, Mar 9, 2016 at 10:27 AM, Remko Popma wrote: > No, I'm in Sydney. > > On Wed, Mar 9, 2016 at 9:41 AM, Gary Gregory > wrote: > >> Are you in SoCal perchance? >> >> Gary >> > >

Re: Fast and Furious

No, I'm in Sydney. On Wed, Mar 9, 2016 at 9:41 AM, Gary Gregory wrote: > Are you in SoCal perchance? > > Gary >

Re: Fast and Furious

Are you in SoCal perchance? Gary

Jenkins build became unstable: Log4j 2.x #1779

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

[jira] [Commented] (LOG4J2-1200) Kill process with Socket Appender causes flood of Connection-Reset logs

[ https://issues.apache.org/jira/browse/LOG4J2-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185930#comment-15185930 ] Mauro Rocco commented on LOG4J2-1200: - [~jvz] thanks. Can I help with that ? > Kill

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185922#comment-15185922 ] Matt Sicker commented on LOG4J2-1116: - Ah good point, though I believe this scenario

Re: Fast and Furious

Some of the recent changes were to fix issues introduced by the reusable message idea. It is good that we are not rushing this release, and thanks everyone for your patience. I originally wanted to make GC-free mode the default to begin with, but it may be smart to initially require that users swi

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185916#comment-15185916 ] Remko Popma commented on LOG4J2-1116: - Same here but some people don't have that luxu

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185914#comment-15185914 ] Matt Sicker commented on LOG4J2-1116: - You can still use ThreadLocal in a web app as

[jira] [Commented] (LOG4J2-851) Create RollingMemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185890#comment-15185890 ] Remko Popma commented on LOG4J2-851: Hmm, this ticket is about adding a rolling versio

[jira] [Resolved] (LOG4J2-1160) LoggerContext logs with FATAL priority when unable to register a shutdown hook

[ https://issues.apache.org/jira/browse/LOG4J2-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1160. - Resolution: Fixed Fix Version/s: 2.6 > LoggerContext logs with FATAL priority when unable

[jira] [Commented] (LOG4J2-1160) LoggerContext logs with FATAL priority when unable to register a shutdown hook

[ https://issues.apache.org/jira/browse/LOG4J2-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185888#comment-15185888 ] Matt Sicker commented on LOG4J2-1160: - I searched the project and the only other call

[jira] [Commented] (LOG4J2-1160) LoggerContext logs with FATAL priority when unable to register a shutdown hook

[ https://issues.apache.org/jira/browse/LOG4J2-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185884#comment-15185884 ] Remko Popma commented on LOG4J2-1160: - I did not check the rest, but based on Gary's

[jira] [Commented] (LOG4J2-1160) LoggerContext logs with FATAL priority when unable to register a shutdown hook

[ https://issues.apache.org/jira/browse/LOG4J2-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185874#comment-15185874 ] Matt Sicker commented on LOG4J2-1160: - Then that covers everything. We could probably

[jira] [Commented] (LOG4J2-1160) LoggerContext logs with FATAL priority when unable to register a shutdown hook

[ https://issues.apache.org/jira/browse/LOG4J2-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185858#comment-15185858 ] Remko Popma commented on LOG4J2-1160: - Thanks for the reminder! I fixed the async log

[jira] [Commented] (LOG4J2-869) Monitor contention at org.apache.logging.log4j.core.util.Loader.*

[ https://issues.apache.org/jira/browse/LOG4J2-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185818#comment-15185818 ] Matt Sicker commented on LOG4J2-869: ClassLoader.loadClass() also uses a lock, though

Re: [10/10] logging-log4j2 git commit: Unit test for GelfLayout.encode

On Wed, Mar 9, 2016 at 3:35 AM, wrote: > Unit test for GelfLayout.encode > > > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo > Commit: > http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/58152b79 > Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/5

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185784#comment-15185784 ] Remko Popma commented on LOG4J2-1116: - Linking this issue as Related To LOG4J2-1270.

[jira] [Commented] (LOG4J2-1133) In page "Configuration", section "Property Substitution", add "jndi" context

[ https://issues.apache.org/jira/browse/LOG4J2-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185751#comment-15185751 ] Matt Sicker commented on LOG4J2-1133: - We don't do snapshot builds of the website, bu

[jira] [Resolved] (LOG4J2-248) Log4jWebInitializerImpl: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-248. Resolution: Fixed Fix Version/s: 2.6 Fixed in master. Please verify and close. > Log4jWebIni

[jira] [Updated] (LOG4J2-248) Log4jWebInitializerImpl: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-248: --- Summary: Log4jWebInitializerImpl: Use Thread instead of Class for fallback classloader (was: Log4jCon

[jira] [Assigned] (LOG4J2-248) Log4jWebInitializerImpl: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-248: -- Assignee: Matt Sicker > Log4jWebInitializerImpl: Use Thread instead of Class for fallback class

[jira] [Commented] (LOG4J2-400) [OSGi] Provide Appender-Bundles

[ https://issues.apache.org/jira/browse/LOG4J2-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185726#comment-15185726 ] Matt Sicker commented on LOG4J2-400: I don't think this issue is feasible anymore. May

[jira] [Commented] (LOG4J2-516) As a developer using OSGi, I want to use Log4J as my OSGi Log Service

[ https://issues.apache.org/jira/browse/LOG4J2-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185723#comment-15185723 ] Matt Sicker commented on LOG4J2-516: Well, there are two approaches now: # pax-loggin

[jira] [Commented] (LOG4J2-533) Remove unused code

[ https://issues.apache.org/jira/browse/LOG4J2-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185720#comment-15185720 ] Matt Sicker commented on LOG4J2-533: Patch no longer applies, though there is a class

[jira] [Updated] (LOG4J2-534) As an Amazon Web Services user, I want a DynamoDB NoSQL appender

[ https://issues.apache.org/jira/browse/LOG4J2-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-534: --- Issue Type: New Feature (was: Story) > As an Amazon Web Services user, I want a DynamoDB NoSQL append

[jira] [Commented] (LOG4J2-586) Capability to merge LoggerContexts or dynamically add an additional ConfigurationSource to a context.

[ https://issues.apache.org/jira/browse/LOG4J2-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185707#comment-15185707 ] Matt Sicker commented on LOG4J2-586: This sounds like a duplicate of LOG4J2-494 or wou

[jira] [Closed] (LOG4J2-606) Consider moving log4j-core SPI-like classes to its own package.

[ https://issues.apache.org/jira/browse/LOG4J2-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-606. -- Resolution: Won't Fix Way too late to be moving classes like these around. No big deal, anyway. > Consi

[jira] [Commented] (LOG4J2-618) Solr Appender

[ https://issues.apache.org/jira/browse/LOG4J2-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185698#comment-15185698 ] Matt Sicker commented on LOG4J2-618: Could you update this patch based on the latest m

[jira] [Commented] (LOG4J2-1133) In page "Configuration", section "Property Substitution", add "jndi" context

[ https://issues.apache.org/jira/browse/LOG4J2-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185693#comment-15185693 ] Fabien Baligand commented on LOG4J2-1133: - Hi, Thank you for resolving the issue

[jira] [Commented] (LOG4J2-633) Need to check permissions when registering shutdown hooks and obtaining classloaders

[ https://issues.apache.org/jira/browse/LOG4J2-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185692#comment-15185692 ] Matt Sicker commented on LOG4J2-633: Looks like this should be added to DefaultShutdow

[jira] [Updated] (LOG4J2-677) Upgrade LightCouch to 0.1.x

[ https://issues.apache.org/jira/browse/LOG4J2-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-677: --- Description: They're at version 0.1.8 now. (was: They're at version 0.1.3 now.) > Upgrade LightCouch

[jira] [Commented] (LOG4J2-806) XML Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185666#comment-15185666 ] Matt Sicker commented on LOG4J2-806: Comma-separated, spaces are allowed. Is this not

[jira] [Commented] (LOG4J2-851) Create RollingMemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185650#comment-15185650 ] Matt Sicker commented on LOG4J2-851: Would this be useful to include in the GC-free ep

[jira] [Commented] (LOG4J2-860) Unify plugin builders and plugin factories

[ https://issues.apache.org/jira/browse/LOG4J2-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185645#comment-15185645 ] Matt Sicker commented on LOG4J2-860: I'd actually prefer to do this after we go Java 1

[jira] [Closed] (LOG4J2-863) FindBugs build fails on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-863. -- Resolution: Fixed We're on findbugs 3.0.3 currently and Java 7, I build with Java 8 all the time, works

Re: version 1.2 vs 2 properties files thoughts

You should be able to tell just by looking for “log4j.” as the prefix. Log4j 2 doesn’t do that anywhere. Ralph > On Mar 8, 2016, at 12:44 PM, Gary Gregory wrote: > > Yes, I can make it work by looking for "log4j.rootLogger" for example, and I > guess if the v2 format changes we can add a prop

[jira] [Commented] (LOG4J2-906) Adding TelnetAppender

[ https://issues.apache.org/jira/browse/LOG4J2-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185629#comment-15185629 ] Matt Sicker commented on LOG4J2-906: This doesn't look too hard to port, but what's th

Re: version 1.2 vs 2 properties files thoughts

Yes, I can make it work by looking for "log4j.rootLogger" for example, and I guess if the v2 format changes we can add a property _then_ that says 2.6 or 3.0 or whatever. Gary On Tue, Mar 8, 2016 at 11:39 AM, Matt Sicker wrote: > Well, if the new config format doesn't prefix anything with log4j

Re: version 1.2 vs 2 properties files thoughts

Well, if the new config format doesn't prefix anything with log4j., then that sounds like a safe way to check the version. Adding a version wouldn't work with previously-written formats, so we'd still have to guess. On 8 March 2016 at 13:28, Gary Gregory wrote: > I initially thought of adding a

[jira] [Commented] (LOG4J2-945) Reconfiguring statusLogger to a higher level doesn't work correctly

[ https://issues.apache.org/jira/browse/LOG4J2-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185595#comment-15185595 ] Gary Gregory commented on LOG4J2-945: - FTR, not a PITA! A passionate user :-) > Recon

[jira] [Commented] (LOG4J2-916) Logfile contains information written before last rollover

[ https://issues.apache.org/jira/browse/LOG4J2-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185592#comment-15185592 ] Matt Sicker commented on LOG4J2-916: Do you have an updated solution for this? Rolling

version 1.2 vs 2 properties files thoughts

I initially thought of adding a version=2 to our Log4j 2 properties file format. I am experimenting with code to read in 1.2 properties files to configure Log4j 2, and I'd like an easy way to tell if I'm dealing with a version 2 properly file. I thought that would be cleaner that looking for "lo

[jira] [Commented] (LOG4J2-945) Reconfiguring statusLogger to a higher level doesn't work correctly

[ https://issues.apache.org/jira/browse/LOG4J2-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185574#comment-15185574 ] Matt Sicker commented on LOG4J2-945: Your patch doesn't apply to master anymore. Could

[jira] [Closed] (LOG4J2-989) Update tests to use ActiveMQ from 5.10 to 5.11.1

[ https://issues.apache.org/jira/browse/LOG4J2-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-989. -- Resolution: Fixed Fixed so long ago that we're using ActiveMQ 5.13.0. > Update tests to use ActiveMQ fr

[jira] [Closed] (LOG4J2-990) Update from JUnit 4.11 to 4.12

[ https://issues.apache.org/jira/browse/LOG4J2-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-990. -- Resolution: Fixed Assignee: Matt Sicker Fix Version/s: 2.6 I updated this back in commit

Re: [LOG4J2-1309] Configuration file error does not show cause exception.

I created a unit test for this and it was behaving properly. Ralph > On Mar 8, 2016, at 9:57 AM, Gary Gregory wrote: > > It does not behave properly in 2.5 based on what I say. I did not try master > though, needs investigation... later today or tonight hopefully unless you > get to it first.

[jira] [Commented] (LOG4J2-1206) org.apache.logging.log4j.core.LoggerContext#updateLoggers should call firePropertyChangeEvent

[ https://issues.apache.org/jira/browse/LOG4J2-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185321#comment-15185321 ] Matt Sicker commented on LOG4J2-1206: - Alright, I added a test for it and put this in

Re: [LOG4J2-1309] Configuration file error does not show cause exception.

Remko thinks he knows what might have caused the issue and commented on the bug in jira. On 8 March 2016 at 10:57, Gary Gregory wrote: > It does not behave properly in 2.5 based on what I say. I did not try > master though, needs investigation... later today or tonight hopefully > unless you get

[jira] [Closed] (LOG4J2-1310) JndiLookup mindlessly casts to String and should use String.valueOf()

[ https://issues.apache.org/jira/browse/LOG4J2-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-1310. --- Resolution: Fixed In master. > JndiLookup mindlessly casts to String and should use String.valueOf()

[jira] [Created] (LOG4J2-1310) JndiLookup mindlessly casts to String and should use String.valueOf()

Matt Sicker created LOG4J2-1310: --- Summary: JndiLookup mindlessly casts to String and should use String.valueOf() Key: LOG4J2-1310 URL: https://issues.apache.org/jira/browse/LOG4J2-1310 Project: Log4j 2

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185276#comment-15185276 ] Matt Sicker commented on LOG4J2-1116: - This issue will most likely be completely take

[jira] [Comment Edited] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185276#comment-15185276 ] Matt Sicker edited comment on LOG4J2-1116 at 3/8/16 5:12 PM: -

[jira] [Resolved] (LOG4J2-1133) In page "Configuration", section "Property Substitution", add "jndi" context

[ https://issues.apache.org/jira/browse/LOG4J2-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1133. - Resolution: Fixed Assignee: Matt Sicker Fix Version/s: 2.6 Added in master. Pleas

[jira] [Commented] (LOG4J2-1154) Javadoc for AbstractFilter wrong?

[ https://issues.apache.org/jira/browse/LOG4J2-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185243#comment-15185243 ] Matt Sicker commented on LOG4J2-1154: - filter(LogEvent) is used at the appender level

Re: Fast and Furious

I'm even more concerned now that more of the no-GC changes are coming in, still, fast and furious. I see what smells like a lot of non-OO code fly by here and there: lots if-else-if-else-if-else, as opposed to subclassing or delegation if appropriate. Are we rushing toward this no-GC goal without

[jira] [Commented] (LOG4J2-1206) org.apache.logging.log4j.core.LoggerContext#updateLoggers should call firePropertyChangeEvent

[ https://issues.apache.org/jira/browse/LOG4J2-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185234#comment-15185234 ] Rodrigo Merino commented on LOG4J2-1206: [~jvz] That change looks good to me. It'

Re: [LOG4J2-1309] Configuration file error does not show cause exception.

It does not behave properly in 2.5 based on what I say. I did not try master though, needs investigation... later today or tonight hopefully unless you get to it first. Gary On Tue, Mar 8, 2016 at 6:56 AM, Matt Sicker wrote: > I thought parameterized messages already checked the last param for

[jira] [Commented] (LOG4J2-1160) LoggerContext logs with FATAL priority when unable to register a shutdown hook

[ https://issues.apache.org/jira/browse/LOG4J2-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185221#comment-15185221 ] Matt Sicker commented on LOG4J2-1160: - Looks like Configurator and ProviderUtil use f

Re: Need to update the JIRA project summary

Done. Good catch! G On Tue, Mar 8, 2016 at 8:27 AM, Matt Sicker wrote: > > Apache Log4j 2.0 is the main development branch for logging services > designed for Java 6 and later. > > That should read Java 7. > > -- > Matt Sicker > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java

[jira] [Commented] (LOG4J2-1184) NullPointerException when attempting to configure logging in custom ShutdownCallbackRegistry

[ https://issues.apache.org/jira/browse/LOG4J2-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185217#comment-15185217 ] Matt Sicker commented on LOG4J2-1184: - Is this still an issue or can we close it? >

[jira] [Updated] (LOG4J2-1200) Kill process with Socket Appender causes flood of Connection-Reset logs

[ https://issues.apache.org/jira/browse/LOG4J2-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1200: Attachment: LOG4J2_1200___Kill_process_with_Socket_Appender_causes_flood_of_Connection_Reset_logs.p

[jira] [Resolved] (LOG4J2-1203) Allow filtering of line breaks in layout pattern

[ https://issues.apache.org/jira/browse/LOG4J2-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1203. - Resolution: Duplicate Fix Version/s: 2.0-rc2 Resolving as duplicate. > Allow filtering of

[jira] [Updated] (LOG4J2-1206) org.apache.logging.log4j.core.LoggerContext#updateLoggers should call firePropertyChangeEvent

[ https://issues.apache.org/jira/browse/LOG4J2-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1206: Attachment: LOG4J2_1206___org_apache_logging_log4j_core_LoggerContext_updateLoggers_should_call_fir

Re: GC lean way to convert StringBuilder to byte[]

I did it a bit differently, but now there are unit tests for GelfLayout.encode(). On Tue, Mar 8, 2016 at 3:51 PM, Remko Popma wrote: > I added some tests to PatternLayoutTest, please take a look. > > On Tue, Mar 8, 2016 at 11:56 PM, Mikael Ståldal > wrote: > >> I have done some work on this for

[jira] [Commented] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185175#comment-15185175 ] Matt Sicker commented on LOG4J2-1209: - Any wish to include this issue in 2.6? > Logg

[jira] [Commented] (LOG4J2-1247) Can not build Log4j from git master due to a test failure in Log4j Core

[ https://issues.apache.org/jira/browse/LOG4J2-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185171#comment-15185171 ] Matt Sicker commented on LOG4J2-1247: - Is this still a problem for you? We've been bu

Need to update the JIRA project summary

> Apache Log4j 2.0 is the main development branch for logging services designed for Java 6 and later. That should read Java 7. -- Matt Sicker

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

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

Re: Can't build log4j from IntelliJ, any ideas?

I figured out the issue. You need to run "mvn clean compile" first, then IntelliJ picks up the compiled annotation processor properly. On 2 March 2016 at 09:04, Matt Sicker wrote: > It worked for me after I restarted IntelliJ. Might have been a cache issue > or something. Hopefully I don't get t

[jira] [Commented] (LOG4J2-1309) Configuration file error does not show cause exception

[ https://issues.apache.org/jira/browse/LOG4J2-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185054#comment-15185054 ] Remko Popma commented on LOG4J2-1309: - This may be a bug I introduced when I was addr

Re: Jenkins build is still unstable: Log4j 2.x #1775

Forgot to post "first!" haha On 8 March 2016 at 09:05, Remko Popma wrote: > :-) > > On Wed, Mar 9, 2016 at 2:05 AM, Remko Popma wrote: > >> snap! >> >> On Wed, Mar 9, 2016 at 2:05 AM, Matt Sicker wrote: >> >>> Now we're back to our regularly-scheduled bzip2 test failure. >>> >>> On 8 March 201

Re: Jenkins build is still unstable: Log4j 2.x #1775

snap! On Wed, Mar 9, 2016 at 2:05 AM, Matt Sicker wrote: > Now we're back to our regularly-scheduled bzip2 test failure. > > On 8 March 2016 at 09:03, Apache Jenkins Server > wrote: > >> See >> >> >> ---

[jira] [Commented] (LOG4J2-1309) Configuration file error does not show cause exception

[ https://issues.apache.org/jira/browse/LOG4J2-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185029#comment-15185029 ] Matt Sicker commented on LOG4J2-1309: - This sounds like the actual bug right here. >

Re: Jenkins build is still unstable: Log4j 2.x #1775

:-) On Wed, Mar 9, 2016 at 2:05 AM, Remko Popma wrote: > snap! > > On Wed, Mar 9, 2016 at 2:05 AM, Matt Sicker wrote: > >> Now we're back to our regularly-scheduled bzip2 test failure. >> >> On 8 March 2016 at 09:03, Apache Jenkins Server < >> jenk...@builds.apache.org> wrote: >> >>> See

Re: Jenkins build is still unstable: Log4j 2.x #1775

Looks like we are back to our usual bz2 test failing. On Wed, Mar 9, 2016 at 2:03 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > > - > To unsubscribe, e

Re: Jenkins build is still unstable: Log4j 2.x #1775

Now we're back to our regularly-scheduled bzip2 test failure. On 8 March 2016 at 09:03, Apache Jenkins Server wrote: > See > > > - > To unsubscribe, e-mail: log4j-dev-unsubscr.

Jenkins build is still unstable: Log4j 2.x #1775

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

Re: Error messages when running unit tests

Oh I've been noticing that lately. That doesn't really look good. I get that error everywhere. On 8 March 2016 at 04:34, Mikael Ståldal wrote: > Several unit-tests, such as JsonLayoutTest, give me this error messages: > > ERROR StatusLogger Unrecognized format specifier [thread] > ERROR StatusLo

Re: [LOG4J2-1309] Configuration file error does not show cause exception.

I thought parameterized messages already checked the last param for exception. If it's not being printed out, that sounds like a bug! On 7 March 2016 at 22:29, Gary Gregory wrote: > I've see this pattern: > > LOGGER.error("Error parsing {}", configSource.getLocation(), e); > > Which hides the ex

Re: GC lean way to convert StringBuilder to byte[]

I added some tests to PatternLayoutTest, please take a look. On Tue, Mar 8, 2016 at 11:56 PM, Mikael Ståldal wrote: > I have done some work on this for GelfLayout. Please review branch > gelf-layout-gc-free > > Is there any convenient way to unit-test the encode method of a layout? Do > we do th

[jira] [Comment Edited] (LOG4J2-1296) Add MessageFactory that reuses a cached Message instance

[ https://issues.apache.org/jira/browse/LOG4J2-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184965#comment-15184965 ] Remko Popma edited comment on LOG4J2-1296 at 3/8/16 2:43 PM: -

[jira] [Commented] (LOG4J2-1296) Add MessageFactory that reuses a cached Message instance

[ https://issues.apache.org/jira/browse/LOG4J2-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184965#comment-15184965 ] Remko Popma commented on LOG4J2-1296: - This problem has now been addressed. * LogEven

  1   2   >