[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473122#comment-15473122 ] Gary Gregory commented on LOG4J2-1259: -- Arg, good catch again. Time for rest after a long day. Fixed

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473043#comment-15473043 ] Gary Gregory commented on LOG4J2-1259: -- Hi [~SteffenO]: Nice find and my bad! I implemented

[jira] [Closed] (LOG4J2-1569) Update Jackson from 2.8.1 to 2.8.2

[ https://issues.apache.org/jira/browse/LOG4J2-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1569. Resolution: Fixed In Git master. Local build passes 'mvn clean test'. > Update Jackson from 2.8.1

[jira] [Created] (LOG4J2-1569) Update Jackson from 2.8.1 to 2.8.2

Gary Gregory created LOG4J2-1569: Summary: Update Jackson from 2.8.1 to 2.8.2 Key: LOG4J2-1569 URL: https://issues.apache.org/jira/browse/LOG4J2-1569 Project: Log4j 2 Issue Type: Improvement

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15471328#comment-15471328 ] Gary Gregory commented on LOG4J2-1528: -- I get CR LF for line endings. I also get nasty TABs for

[jira] [Comment Edited] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15471284#comment-15471284 ] Gary Gregory edited comment on LOG4J2-1259 at 9/7/16 5:40 PM: -- Hi

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15471284#comment-15471284 ] Gary Gregory commented on LOG4J2-1259: -- Hi, The method {{RollingFileManager.releaseSub(long,

[jira] [Comment Edited] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470911#comment-15470911 ] Gary Gregory edited comment on LOG4J2-1259 at 9/7/16 3:26 PM: -- I added an

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470917#comment-15470917 ] Gary Gregory commented on LOG4J2-1259: -- I have not seen any prep work on our end for a 2.6.3

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470911#comment-15470911 ] Gary Gregory commented on LOG4J2-1259: -- I added an abstract class {{AbstractTriggeringPolicy}} that

[jira] [Resolved] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1563. -- Resolution: Fixed Fix Version/s: 2.7 In Git master. > Log4j 2.6.2 can lose exceptions

[jira] [Commented] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469276#comment-15469276 ] Gary Gregory commented on LOG4J2-1563: -- Hi, We now have: {code:java} try {

[jira] [Commented] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469270#comment-15469270 ] Gary Gregory commented on LOG4J2-1563: -- The tests restores the Security Manager, which is good.

[jira] [Commented] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469261#comment-15469261 ] Gary Gregory commented on LOG4J2-1563: -- The patch looks good. I'll apply it. Thank you. My next

[jira] [Comment Edited] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469033#comment-15469033 ] Gary Gregory edited comment on LOG4J2-1259 at 9/7/16 12:12 AM: --- I have a

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469033#comment-15469033 ] Gary Gregory commented on LOG4J2-1259: -- I have a tentative fix that lets {{TriggeringPolicy}}

[jira] [Updated] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1086: - Summary: SizeBasedTriggeringPolicy is not working properly (was: SizeBasedTriggeringPolicy is

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466935#comment-15466935 ] Gary Gregory commented on LOG4J2-1528: -- There is still something wrong. It's not critical, but it's

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466625#comment-15466625 ] Gary Gregory commented on LOG4J2-1259: -- If you add our SNAPSHOT repository to your Maven settings,

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15465604#comment-15465604 ] Gary Gregory commented on LOG4J2-1259: -- Hi Steffen: Did you try with the latest from Git master? I

[jira] [Reopened] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1517: -- > Add ThreadContext.setContext(Map) >

[jira] [Reopened] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1517: -- > Add ThreadContext.setContext(Map) >

[jira] [Resolved] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1517. -- Resolution: Later > Add ThreadContext.setContext(Map) >

[jira] [Resolved] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1517. -- Resolution: Fixed > Add ThreadContext.setContext(Map) >

[jira] [Updated] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1517: - Fix Version/s: (was: 2.7) > Add ThreadContext.setContext(Map) >

[jira] [Resolved] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1517. -- Resolution: Later I'm marking this issue as {{Later}} to allow the 2.7 release to move on

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15465273#comment-15465273 ] Gary Gregory commented on LOG4J2-1528: -- Yes, I hard coded EOL to be "\n" instead of

[jira] [Commented] (LOG4J2-1560) Log4j can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15463105#comment-15463105 ] Gary Gregory commented on LOG4J2-1560: -- Go for it :-) I am travelling coast-to-coast today so I will

[jira] [Closed] (LOG4J2-1562) SocketAppender memory usage grows unbounded if it cannot connect to a server

[ https://issues.apache.org/jira/browse/LOG4J2-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1562. Resolution: Fixed Fix Version/s: 2.7 In Git master. > SocketAppender memory usage grows

[jira] [Updated] (LOG4J2-1562) SocketAppender memory usage grows unbounded if it cannot connect to a server

[ https://issues.apache.org/jira/browse/LOG4J2-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1562: - Summary: SocketAppender memory usage grows unbounded if it cannot connect to a server (was:

[jira] [Created] (LOG4J2-1562) SocketAppender memoey usage grows unbounded if it cannot connect to a server

Gary Gregory created LOG4J2-1562: Summary: SocketAppender memoey usage grows unbounded if it cannot connect to a server Key: LOG4J2-1562 URL: https://issues.apache.org/jira/browse/LOG4J2-1562

[jira] [Commented] (LOG4J2-1561) print expected mdc info to each line of the exception stacktrace

[ https://issues.apache.org/jira/browse/LOG4J2-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15461526#comment-15461526 ] Gary Gregory commented on LOG4J2-1561: -- Wouldn't this be better to do through a pattern layout

[jira] [Resolved] (LOG4J2-1559) NPE in Level.isInRange

[ https://issues.apache.org/jira/browse/LOG4J2-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1559. -- Resolution: Fixed Fix Version/s: 2.7 In Git master, Please verify and close. > NPE in

[jira] [Resolved] (LOG4J2-1558) SocketAppender should support IO buffering

[ https://issues.apache.org/jira/browse/LOG4J2-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1558. -- Resolution: Fixed Fix Version/s: 2.7 > SocketAppender should support IO buffering >

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458661#comment-15458661 ] Gary Gregory commented on LOG4J2-1528: -- Nope: {noformat} org.junit.ComparisonFailure:

[jira] [Commented] (LOG4J2-1558) SocketAppender should support IO buffering

[ https://issues.apache.org/jira/browse/LOG4J2-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457398#comment-15457398 ] Gary Gregory commented on LOG4J2-1558: -- Right now, the buffer size for all socket managers is 8K. >

[jira] [Comment Edited] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456677#comment-15456677 ] Gary Gregory edited comment on LOG4J2-1557 at 9/1/16 9:35 PM: -- I'll update

[jira] [Updated] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1557: - Description: Add a {{Builder}} for the {{SocketAppender}} and deprecate the factory method. I

[jira] [Updated] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1557: - Description: Add a Builder for the SocketAppender (deprecates the factory method). I need to

[jira] [Commented] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456677#comment-15456677 ] Gary Gregory commented on LOG4J2-1557: -- I'll update the description. > Add a Builder for the

[jira] [Created] (LOG4J2-1558) SocketAppender should support IO buffering

Gary Gregory created LOG4J2-1558: Summary: SocketAppender should support IO buffering Key: LOG4J2-1558 URL: https://issues.apache.org/jira/browse/LOG4J2-1558 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1553. Resolution: Fixed Closing. > AbstractManager should implement AutoCloseable >

[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=15456182#comment-15456182 ] Gary Gregory commented on LOG4J2-1539: -- I just deleted the Git branch since I merged it into master

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456176#comment-15456176 ] Gary Gregory commented on LOG4J2-1547: -- I just deleted the Git branch now that I merged this in

[jira] [Commented] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456170#comment-15456170 ] Gary Gregory commented on LOG4J2-1553: -- I just deleted the branch now that it is merged. >

[jira] [Updated] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1557: - Description: Add a Builder for the SocketAppender (deprecates the factory method). Deprecated:

[jira] [Resolved] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1557. -- Resolution: Fixed > Add a Builder for the SocketAppender (deprecates factory method) >

[jira] [Closed] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1557. Resolution: Fixed > Add a Builder for the SocketAppender (deprecates factory method) >

[jira] [Reopened] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1557: -- > Add a Builder for the SocketAppender (deprecates factory method) >

[jira] [Updated] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1557: - Description: Add a Builder for the SocketAppender (deprecates the factory method). Deprecated:

[jira] [Updated] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1557: - Description: (was: Add a Builder for the SocketAppender (deprecates the factory method).

[jira] [Reopened] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1557: -- > Add a Builder for the SocketAppender (deprecates factory method) >

[jira] [Closed] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

[ https://issues.apache.org/jira/browse/LOG4J2-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1557. Resolution: Fixed In Git master. > Add a Builder for the SocketAppender (deprecates factory

[jira] [Created] (LOG4J2-1557) Add a Builder for the SocketAppender (deprecates factory method)

Gary Gregory created LOG4J2-1557: Summary: Add a Builder for the SocketAppender (deprecates factory method) Key: LOG4J2-1557 URL: https://issues.apache.org/jira/browse/LOG4J2-1557 Project: Log4j 2

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456007#comment-15456007 ] Gary Gregory commented on LOG4J2-1528: -- Crap, I edited the wrong comment with the new unit test

[jira] [Comment Edited] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455984#comment-15455984 ] Gary Gregory edited comment on LOG4J2-1528 at 9/1/16 5:01 PM: -- No:

[jira] [Comment Edited] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455984#comment-15455984 ] Gary Gregory edited comment on LOG4J2-1528 at 9/1/16 5:00 PM: -- No:

[jira] [Commented] (LOG4J2-1235) org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working correctly

[ https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455700#comment-15455700 ] Gary Gregory commented on LOG4J2-1235: -- Can you track the change to a specific commit? >

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455688#comment-15455688 ] Gary Gregory commented on LOG4J2-1259: -- I've started a new initiative to better manage our Log4j

[jira] [Commented] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire

[ https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455560#comment-15455560 ] Gary Gregory commented on LOG4J2-1548: -- Do consider providing patches, testing the current code (Git

[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=1543#comment-1543 ] Gary Gregory commented on LOG4J2-1349: -- I like it :) > Garbage-free ThreadContext map >

[jira] [Closed] (LOG4J2-1556) Custom Log4j threads should extend Log4jThread

[ https://issues.apache.org/jira/browse/LOG4J2-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1556. Resolution: Fixed In Git master. > Custom Log4j threads should extend Log4jThread >

[jira] [Created] (LOG4J2-1556) Custom Log4j threads should extend Log4jThread

Gary Gregory created LOG4J2-1556: Summary: Custom Log4j threads should extend Log4jThread Key: LOG4J2-1556 URL: https://issues.apache.org/jira/browse/LOG4J2-1556 Project: Log4j 2 Issue Type:

[jira] [Comment Edited] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452907#comment-15452907 ] Gary Gregory edited comment on LOG4J2-1528 at 8/31/16 6:01 PM: --- Broken unit

[jira] [Reopened] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1528: -- Broken unit test (on Windows 7 for me): {code:java} java.lang.AssertionError: Expected: Expected

[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=15452585#comment-15452585 ] Gary Gregory edited comment on LOG4J2-1349 at 8/31/16 3:47 PM: --- Coming in

[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=15452585#comment-15452585 ] Gary Gregory commented on LOG4J2-1349: -- Comming in late in the thread. I like the idea of the

[jira] [Commented] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire

[ https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452573#comment-15452573 ] Gary Gregory commented on LOG4J2-1548: -- Yes, change is risk and lots of changes compound the risk.

[jira] [Commented] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448077#comment-15448077 ] Gary Gregory commented on LOG4J2-1553: -- This branch is good to go IMO. I'll wait another day or so

[jira] [Updated] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1553: - Description: The class {{AbstractManager}} should implement {{java.lang.AutoCloseable}}. A

[jira] [Commented] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire

[ https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446905#comment-15446905 ] Gary Gregory commented on LOG4J2-1548: -- I applied the patch

[jira] [Commented] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446894#comment-15446894 ] Gary Gregory commented on LOG4J2-1553: -- In the branch, the Javadoc now reads: {code:java} /** *

[jira] [Resolved] (LOG4J2-1502) CsvParameterLayout and CsvLogEventLayout insert NUL character if data starts with {, (, [ or "

[ https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1502. -- Resolution: Fixed Fix Version/s: 2.7 Fixed in Git master. Please verify and close. >

[jira] [Commented] (LOG4J2-1502) CsvParameterLayout and CsvLogEventLayout insert NUL character if data starts with {, (, [ or "

[ https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446867#comment-15446867 ] Gary Gregory commented on LOG4J2-1502: -- This issue also applies to {{CsvLogEventLayout}}. >

[jira] [Updated] (LOG4J2-1502) CsvParameterLayout and CsvLogEventLayout insert NUL character if data starts with {, (, [ or "

[ https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1502: - Summary: CsvParameterLayout and CsvLogEventLayout insert NUL character if data starts with {, (,

[jira] [Commented] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446708#comment-15446708 ] Gary Gregory commented on LOG4J2-1553: -- Thank you [~rem...@yahoo.com] for the careful review and

[jira] [Resolved] (LOG4J2-1235) org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working correctly

[ https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1235. -- Resolution: Fixed Fix Version/s: 2.7 In Git master. Please verify and close. >

[jira] [Updated] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1553: - Description: The class {{AbstractManager}} should implement {{java.lang.AutoCloseable}}. A

[jira] [Updated] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1553: - Description: The class {{AbstractManager}} should implement {{java.lang.AutoCloseable}}. A

[jira] [Comment Edited] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446644#comment-15446644 ] Gary Gregory edited comment on LOG4J2-1553 at 8/29/16 6:30 PM: --- A short

[jira] [Updated] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1553: - Description: The class {{AbstractManager}} should implement {{java.lang.AutoCloseable}}. A

[jira] [Commented] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446644#comment-15446644 ] Gary Gregory commented on LOG4J2-1553: -- A short lived object depends on your perspective. For

[jira] [Commented] (LOG4J2-1554) org.apache.logging.log4j.core.filter.DynamicThresholdFilter doesn't override all 'filter' methods of org.apache.logging.log4j.core.filter.AbstractFilter

[ https://issues.apache.org/jira/browse/LOG4J2-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446465#comment-15446465 ] Gary Gregory commented on LOG4J2-1554: -- Sergey, This sounds like the same issue as [LOG4J2-1511].

[jira] [Commented] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444854#comment-15444854 ] Gary Gregory commented on LOG4J2-1553: -- (On my phone) the commits are supposed to be in a branch.

[jira] [Commented] (LOG4J2-1502) CsvParameterLayout is inserting NUL character if data starts with {, (, [ or "

[ https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444161#comment-15444161 ] Gary Gregory commented on LOG4J2-1502: -- I think the problem is that a 0x00 is written for the header

[jira] [Commented] (LOG4J2-1502) CsvParameterLayout is inserting NUL character if data starts with {, (, [ or "

[ https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444157#comment-15444157 ] Gary Gregory commented on LOG4J2-1502: -- Might have found something with

[jira] [Comment Edited] (LOG4J2-1502) CsvParameterLayout is inserting NUL character if data starts with {, (, [ or "

[ https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444157#comment-15444157 ] Gary Gregory edited comment on LOG4J2-1502 at 8/28/16 9:31 PM: --- Might have

[jira] [Commented] (LOG4J2-1553) AbstractManager should implement AutoCloseable

[ https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444097#comment-15444097 ] Gary Gregory commented on LOG4J2-1553: -- Implemented in branch {{LOG4J2-1553}}. > AbstractManager

[jira] [Created] (LOG4J2-1553) AbstractManager should implement AutoCloseable

Gary Gregory created LOG4J2-1553: Summary: AbstractManager should implement AutoCloseable Key: LOG4J2-1553 URL: https://issues.apache.org/jira/browse/LOG4J2-1553 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-1552) Help Apache Camel project to upgrade from Log4j 1.x to 2.x

Gary Gregory created LOG4J2-1552: Summary: Help Apache Camel project to upgrade from Log4j 1.x to 2.x Key: LOG4J2-1552 URL: https://issues.apache.org/jira/browse/LOG4J2-1552 Project: Log4j 2

[jira] [Resolved] (LOG4J2-1511) DynamicThresholdFilter filters incorrectly when params are passed as individual arguments instead of varargs

[ https://issues.apache.org/jira/browse/LOG4J2-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1511. -- Resolution: Fixed Fix Version/s: 2.7 In Git master. Please verify and close. >

[jira] [Commented] (LOG4J2-1487) Log4j RollingFileAppender every minute

[ https://issues.apache.org/jira/browse/LOG4J2-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440703#comment-15440703 ] Gary Gregory commented on LOG4J2-1487: -- Hello [~elamas]: Would it be possible for you to test this

[jira] [Commented] (LOG4J2-1535) KafkaAppender NullPointerException when putting the related jars in tomcat lib

[ https://issues.apache.org/jira/browse/LOG4J2-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440660#comment-15440660 ] Gary Gregory commented on LOG4J2-1535: -- Since the NPE is in Kafka code, have you logged a ticket

[jira] [Issue Comment Deleted] (LOG4J2-1535) KafkaAppender NullPointerException when putting the related jars in tomcat lib

[ https://issues.apache.org/jira/browse/LOG4J2-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1535: - Comment: was deleted (was: Since the NPE is in Kafka code, have you logged a ticket with the

[jira] [Commented] (LOG4J2-1502) CsvParameterLayout is inserting NUL character if data starts with {, (, [ or "

[ https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440369#comment-15440369 ] Gary Gregory commented on LOG4J2-1502: -- Hello [~sumit23], I added a passing test: Please see

[jira] [Closed] (LOG4J2-1551) Update JMS test from ActiveMQ 5.13.4 to 5.14.0.

[ https://issues.apache.org/jira/browse/LOG4J2-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1551. Resolution: Fixed Local build OK. In Git master. > Update JMS test from ActiveMQ 5.13.4 to

[jira] [Created] (LOG4J2-1551) Update JMS test from ActiveMQ 5.13.4 to 5.14.0.

Gary Gregory created LOG4J2-1551: Summary: Update JMS test from ActiveMQ 5.13.4 to 5.14.0. Key: LOG4J2-1551 URL: https://issues.apache.org/jira/browse/LOG4J2-1551 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire

[ https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439966#comment-15439966 ] Gary Gregory commented on LOG4J2-1548: -- Please verify and close. Gary > [CronTriggeringPolicy]

[jira] [Commented] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire

[ https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439963#comment-15439963 ] Gary Gregory commented on LOG4J2-1548: -- [~phymbert], Patch applied, thank you and keep' em coming!

[jira] [Resolved] (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 resolved LOG4J2-1539. -- Resolution: Fixed In Git master. > Add Core API Configurator.shutdown(LoggerContext, long,

<    1   2   3   4   5   6   7   8   9   10   >