[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205995#comment-16205995 ] Matt Sicker commented on LOG4J2-2072: - Info about builders: https://logging.apache.org/log4j/2.x

[jira] [Comment Edited] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205976#comment-16205976 ] Gary Gregory edited comment on LOG4J2-2072 at 10/16/17 2:29 PM: IMO

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205976#comment-16205976 ] Gary Gregory commented on LOG4J2-2072: -- IMO, the first task in this ticket should be to convert

[jira] [Commented] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205886#comment-16205886 ] Vincent Thiery commented on LOGCXX-493: --- Awesome! Thanks > Documentation claiming `getTimeSt

[jira] [Resolved] (LOGCXX-361) 15-16 milliseconds granularity on Windows‏

[ https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-361. -- Resolution: Not A Problem log4cxx uses apr_time_now which provides microseconds

[jira] [Resolved] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-493. -- Resolution: Fixed Thanks for the report, I fixed this in master and latest_stable

[jira] [Updated] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning updated LOGCXX-493: - Fix Version/s: 0.11.0 > Documentation claiming `getTimeStamp` is in milliseco

[jira] [Assigned] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning reassigned LOGCXX-493: Assignee: Thorsten Schöning > Documentation claiming `getTimeSt

[jira] [Updated] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Thiery updated LOGCXX-493: -- Summary: Documentation claiming `getTimeStamp` is in milliseconds but actually

[jira] [Created] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but really is in microseconds

Vincent Thiery created LOGCXX-493: - Summary: Documentation claiming `getTimeStamp` is in milliseconds but really is in microseconds Key: LOGCXX-493 URL: https://issues.apache.org/jira/browse/LOGCXX-493

[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender

[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205320#comment-16205320 ] Ralph Goers commented on LOG4J2-2076: - I wasn't thinking that nosql would generate a jar. I would

[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender

[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205309#comment-16205309 ] Matt Sicker commented on LOG4J2-2076: - It could be. All the classes directly in this package: https

[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender

[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205301#comment-16205301 ] Ralph Goers commented on LOG4J2-2076: - Does it make sense to make nosql a multi-module parent

[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender

[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205300#comment-16205300 ] Matt Sicker commented on LOG4J2-2076: - You may want to move some of the common code back in to log4j

[jira] [Created] (LOG4J2-2076) Split up log4j-nosql into one module per appender

Mikael Ståldal created LOG4J2-2076: -- Summary: Split up log4j-nosql into one module per appender Key: LOG4J2-2076 URL: https://issues.apache.org/jira/browse/LOG4J2-2076 Project: Log4j 2

[jira] [Created] (LOG4J2-2075) Add module information to extended stack trace.

Ralph Goers created LOG4J2-2075: --- Summary: Add module information to extended stack trace. Key: LOG4J2-2075 URL: https://issues.apache.org/jira/browse/LOG4J2-2075 Project: Log4j 2 Issue Type

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205120#comment-16205120 ] ASF subversion and git services commented on LOG4J2-2056: - Commit

[jira] [Commented] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205113#comment-16205113 ] Remko Popma commented on LOG4J2-2060: - I've committed a fix to master. It would be great if you could

[jira] [Commented] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205112#comment-16205112 ] ASF subversion and git services commented on LOG4J2-2060: - Commit

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205078#comment-16205078 ] Jorge Sanchez commented on LOG4J2-2062: --- I have created a new PR for the key lookup capability

[jira] [Commented] (LOG4J2-2067) Using PatternSelectors breaks header printing in PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205055#comment-16205055 ] Paul Burrowes commented on LOG4J2-2067: --- This tests the patch. I would create a PR but I'm a bit

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205050#comment-16205050 ] ASF subversion and git services commented on LOG4J2-2056: - Commit

[jira] [Resolved] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2056. - Resolution: Fixed Fix Version/s: 2.10.0 Fix has been committed. > Modularize Lo

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2056: Description: To fully support Java 9 all Log4j jars must (at least) be packaged as automatic

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204848#comment-16204848 ] Ralph Goers edited comment on LOG4J2-2056 at 10/14/17 11:09 PM: Another

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204740#comment-16204740 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

[jira] [Resolved] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1431. - Resolution: Fixed Fix Version/s: 2.10.0 Merged to master. > Simplify log4j sys

[jira] [Resolved] (LOG4J2-1809) Add global configuration environment SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1809. - Resolution: Fixed Fix Version/s: 2.10.0 Merged to master. > Add global configurat

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204743#comment-16204743 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204741#comment-16204741 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

[jira] [Commented] (LOG4J2-2074) The console appender should say why it cannot load JAnsi

[ https://issues.apache.org/jira/browse/LOG4J2-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204197#comment-16204197 ] ASF subversion and git services commented on LOG4J2-2074: - Commit

[jira] [Closed] (LOG4J2-2074) The console appender should say why it cannot load JAnsi

[ https://issues.apache.org/jira/browse/LOG4J2-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2074. Resolution: Fixed Fix Version/s: 2.10.0 In git master. > The console appender should

[jira] [Created] (LOG4J2-2074) The console appender should say why it cannot load JAnsi

Gary Gregory created LOG4J2-2074: Summary: The console appender should say why it cannot load JAnsi Key: LOG4J2-2074 URL: https://issues.apache.org/jira/browse/LOG4J2-2074 Project: Log4j 2

[jira] [Closed] (LOG4J2-2073) Log4j-config.xsd should make AppenderRef optional for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2073. Resolution: Fixed Fix Version/s: 2.10.0 In git master. > Log4j-config.xsd should m

[jira] [Commented] (LOG4J2-2073) Log4j-config.xsd should make AppenderRef optional for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204187#comment-16204187 ] ASF subversion and git services commented on LOG4J2-2073: - Commit

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204073#comment-16204073 ] Mikael Ståldal commented on LOG4J2-2062: The first PR is now merged. > Add possibil

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204070#comment-16204070 ] ASF subversion and git services commented on LOG4J2-2062: - Commit

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204062#comment-16204062 ] ASF GitHub Bot commented on LOG4J2-2062: Github user mikaelstaldal commented on the issue

[jira] [Commented] (LOG4J2-1982) Log4j-config.xsd only allows one AppenderRef element for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202777#comment-16202777 ] Gary Gregory commented on LOG4J2-1982: -- Right! Fixing with https://issues.apache.org/jira/browse

[jira] [Created] (LOG4J2-2073) Log4j-config.xsd should make AppenderRef optional for each Logger element

Gary Gregory created LOG4J2-2073: Summary: Log4j-config.xsd should make AppenderRef optional for each Logger element Key: LOG4J2-2073 URL: https://issues.apache.org/jira/browse/LOG4J2-2073 Project

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202771#comment-16202771 ] Ralph Goers edited comment on LOG4J2-2056 at 10/12/17 11:07 PM: What you

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202771#comment-16202771 ] Ralph Goers commented on LOG4J2-2056: - What you described is pretty much how Log4j already works

[jira] [Resolved] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1216. -- Resolution: Fixed PR 116 applied. Please verify and close. Note that the unit test

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202675#comment-16202675 ] ASF subversion and git services commented on LOG4J2-1216: - Commit

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202658#comment-16202658 ] Neil Bartlett commented on LOG4J2-2056: --- Whatever name you choose, that is the name that modules

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202635#comment-16202635 ] Ralph Goers edited comment on LOG4J2-2056 at 10/12/17 9:19 PM

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202635#comment-16202635 ] Ralph Goers commented on LOG4J2-2056: - [~njbartlett] Thanks for jumping in. The options are listed

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202609#comment-16202609 ] Neil Bartlett commented on LOG4J2-2056: --- Joining this thread as I see my name being invoked... I

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202534#comment-16202534 ] Jorge Sanchez commented on LOG4J2-2062: --- Thank you for your comments I really appreciate them

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202397#comment-16202397 ] Ralph Goers commented on LOG4J2-2056: - Yes, an empty Automatic-Module-Name. That seems possibly

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202304#comment-16202304 ] Matt Sicker commented on LOG4J2-2072: - Take a look at the TLS/SSL support classes in core for some

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202207#comment-16202207 ] Gary Gregory commented on LOG4J2-2072: -- Thank you for helping out. Please do not forget unit tests

[jira] [Reopened] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1216: -- > Nested pattern layout options bro

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202165#comment-16202165 ] Stephen Colebourne commented on LOG4J2-2056: 1. Do you mean having an empty Automatic-Module

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202061#comment-16202061 ] Frank Swanson commented on LOG4J2-2072: --- I will put it together shortly(Hopefully this weekend

[jira] [Comment Edited] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201806#comment-16201806 ] Georg Friedrich edited comment on LOG4J2-1216 at 10/12/17 11:23 AM

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201806#comment-16201806 ] Georg Friedrich commented on LOG4J2-1216: - Hi guys, you just introduced an endless parsing

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201802#comment-16201802 ] ASF GitHub Bot commented on LOG4J2-1216: GitHub user GFriedrich opened a pull request: https

[jira] [Commented] (LOG4J2-1982) Log4j-config.xsd only allows one AppenderRef element for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201746#comment-16201746 ] Patrick Lucas commented on LOG4J2-1982: --- Shouldn't this have {{minOccurs="0"}} sinc

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201429#comment-16201429 ] Ralph Goers commented on LOG4J2-2072: - Patches are always welcome. > Support TLS configurat

[jira] [Updated] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Swanson updated LOG4J2-2072: -- Description: When using the FlumeAppnder with a FlumeAvroManager it would be nice to be able

[jira] [Updated] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Swanson updated LOG4J2-2072: -- Description: When using the FlumeAppnder with a FlumeAvroManager it would be nice to be able

[jira] [Created] (LOG4J2-2072) Support TLS configuration through FlumeAppender

Frank Swanson created LOG4J2-2072: - Summary: Support TLS configuration through FlumeAppender Key: LOG4J2-2072 URL: https://issues.apache.org/jira/browse/LOG4J2-2072 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-2068) Can't set monitorInterval for composite XML configuration.

[ https://issues.apache.org/jira/browse/LOG4J2-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201184#comment-16201184 ] Robert Haycock commented on LOG4J2-2068: I created a branch but can't push, keep getting

[jira] [Commented] (LOG4J2-2071) Add org.apache.logging.log4j.core.config.composite.CompositeConfiguration#toString()

[ https://issues.apache.org/jira/browse/LOG4J2-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201065#comment-16201065 ] Gary Gregory commented on LOG4J2-2071: -- This closes #114. >

[jira] [Commented] (LOG4J2-2071) Add org.apache.logging.log4j.core.config.composite.CompositeConfiguration#toString()

[ https://issues.apache.org/jira/browse/LOG4J2-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201062#comment-16201062 ] ASF GitHub Bot commented on LOG4J2-2071: Github user garydgregory commented on the issue

[jira] [Commented] (LOG4J2-2071) Add org.apache.logging.log4j.core.config.composite.CompositeConfiguration#toString()

[ https://issues.apache.org/jira/browse/LOG4J2-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201061#comment-16201061 ] ASF subversion and git services commented on LOG4J2-2071: - Commit

[jira] [Created] (LOG4J2-2071) Add org.apache.logging.log4j.core.config.composite.CompositeConfiguration#toString()

Gary Gregory created LOG4J2-2071: Summary: Add org.apache.logging.log4j.core.config.composite.CompositeConfiguration#toString() Key: LOG4J2-2071 URL: https://issues.apache.org/jira/browse/LOG4J2-2071

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

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201047#comment-16201047 ] ASF GitHub Bot commented on LOG4J2-2036: Github user asfgit closed the pull request

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

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201046#comment-16201046 ] ASF subversion and git services commented on LOG4J2-2036: - Commit

[jira] [Resolved] (LOG4J2-2068) Can't set monitorInterval for composite XML configuration.

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200958#comment-16200958 ] ASF GitHub Bot commented on LOG4J2-2036: Github user garydgregory commented on the issue

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

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200847#comment-16200847 ] ASF GitHub Bot commented on LOG4J2-2036: Github user cakofony commented on the issue: https

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

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200846#comment-16200846 ] ASF GitHub Bot commented on LOG4J2-2036: GitHub user cakofony opened a pull request: https

[jira] [Commented] (LOG4J2-2068) Can't set monitorInterval for composite XML configuration.

[ https://issues.apache.org/jira/browse/LOG4J2-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200540#comment-16200540 ] Gary Gregory commented on LOG4J2-2068: -- Hi [~tedtrippin]: Thank you for your patch! Can you please

[jira] [Updated] (LOG4J2-2070) Log4j1XmlLayout does not provide the entire stack trace, it is missing the caused by information

[ https://issues.apache.org/jira/browse/LOG4J2-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2070: - Fix Version/s: 2.9.2 > Log4j1XmlLayout does not provide the entire stack trace, it is miss

[jira] [Resolved] (LOG4J2-2070) Log4j1XmlLayout does not provide the entire stack trace, it is missing the caused by information

[ https://issues.apache.org/jira/browse/LOG4J2-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2070. -- Resolution: Fixed In git master. Please verify and close. > Log4j1XmlLayout does not prov

[jira] [Commented] (LOG4J2-2053) Exception java.nio.charset.UnsupportedCharsetException: cp65001 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200439#comment-16200439 ] ASF subversion and git services commented on LOG4J2-2053: - Commit

[jira] [Comment Edited] (LOG4J2-2068) Can't set monitorInterval for composite XML configuration.

[ https://issues.apache.org/jira/browse/LOG4J2-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200293#comment-16200293 ] Robert Haycock edited comment on LOG4J2-2068 at 10/11/17 2:52 PM

[jira] [Updated] (LOG4J2-2068) Can't set monitorInterval for composite XML configuration.

[ https://issues.apache.org/jira/browse/LOG4J2-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Haycock updated LOG4J2-2068: --- Attachment: patch_2068.diff This patch fixes the problem for me. > Can't

[jira] [Commented] (LOG4J2-2061) RollingFileManager not removed when RollingFileAppender is stopped, using DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200248#comment-16200248 ] Matthew Hill commented on LOG4J2-2061: -- Hi [~garydgregory] Please see attached a sample junit

[jira] [Updated] (LOG4J2-2061) RollingFileManager not removed when RollingFileAppender is stopped, using DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Hill updated LOG4J2-2061: - Attachment: Log4jIssue.zip > RollingFileManager not removed when RollingFileAppender is stop

[jira] [Updated] (LOG4J2-2070) Log4j1XmlLayout does not provide the entire stack trace, it is missing the caused by information

[ https://issues.apache.org/jira/browse/LOG4J2-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Hughes updated LOG4J2-2070: Attachment: patch.diff > Log4j1XmlLayout does not provide the entire stack trace, it is miss

[jira] [Created] (LOG4J2-2070) Log4j1XmlLayout does not provide the entire stack trace, it is missing the caused by information

Doug Hughes created LOG4J2-2070: --- Summary: Log4j1XmlLayout does not provide the entire stack trace, it is missing the caused by information Key: LOG4J2-2070 URL: https://issues.apache.org/jira/browse/LOG4J2-2070

[jira] [Updated] (LOG4J2-2069) --multi-release option not set for the multi-release jar.

[ https://issues.apache.org/jira/browse/LOG4J2-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naman Nigam updated LOG4J2-2069: Summary: --multi-release option not set for the multi-release jar. (was: --multi-release option

[jira] [Created] (LOG4J2-2069) --multi-release option not set for the MultiRelease jar.

Naman Nigam created LOG4J2-2069: --- Summary: --multi-release option not set for the MultiRelease jar. Key: LOG4J2-2069 URL: https://issues.apache.org/jira/browse/LOG4J2-2069 Project: Log4j 2

[jira] [Commented] (LOG4J2-2053) Exception java.nio.charset.UnsupportedCharsetException: cp65001 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199873#comment-16199873 ] Frank Steudle commented on LOG4J2-2053: --- Thank you for your endeavours! My runtime is Oracle Java

[jira] [Commented] (LOG4J2-2060) AbstactDatabase appender issue with AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199870#comment-16199870 ] Tolga Kavukcu commented on LOG4J2-2060: --- Sure i can provide the unit test case. > AbstactDatab

[jira] [Commented] (LOG4J2-2061) RollingFileManager not removed when RollingFileAppender is stopped, using DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199534#comment-16199534 ] Gary Gregory commented on LOG4J2-2061: -- Hi [~matthewhill], Are you able to provide a unit test

[jira] [Comment Edited] (LOG4J2-2067) Using PatternSelectors breaks header printing in PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199531#comment-16199531 ] Gary Gregory edited comment on LOG4J2-2067 at 10/10/17 11:03 PM: - Would

[jira] [Commented] (LOG4J2-2053) Exception java.nio.charset.UnsupportedCharsetException: cp65001 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199526#comment-16199526 ] Gary Gregory commented on LOG4J2-2053: -- Please run the test

[jira] [Commented] (LOG4J2-2053) Exception java.nio.charset.UnsupportedCharsetException: cp65001 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199522#comment-16199522 ] ASF subversion and git services commented on LOG4J2-2053: - Commit

[jira] [Updated] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1216: - Affects Version/s: 2.9.1 > Nested pattern layout options bro

[jira] [Resolved] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1216. -- Resolution: Fixed Fix Version/s: 2.9.2 Setting to Resolved: Fixed in git master

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199473#comment-16199473 ] ASF subversion and git services commented on LOG4J2-1216: - Commit

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2056: - Description: To fully support Java 9 all Log4j jars must (at least) be packaged as automatic

[jira] [Commented] (LOG4J2-2068) Can't set monitorInterval for composite XML configuration.

[ https://issues.apache.org/jira/browse/LOG4J2-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199037#comment-16199037 ] Matt Sicker commented on LOG4J2-2068: - You can use the LoggerContextRule in log4j-core:test

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198885#comment-16198885 ] Ralph Goers commented on LOG4J2-2056: - [~scolebou...@joda.org] Wow - Thanks for taking the time to do

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198790#comment-16198790 ] Stephen Colebourne commented on LOG4J2-2056: I've written up a wiki page with both SLF4J

[jira] [Commented] (LOG4J2-2068) Can't set monitorInterval for composite XML configuration.

[ https://issues.apache.org/jira/browse/LOG4J2-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198415#comment-16198415 ] Robert Haycock commented on LOG4J2-2068: Apart from having a quick look at the code, I don't

  1   2   3   4   5   6   7   8   9   10   >