[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

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

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

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

[jira] [Commented] (LOG4J2-1876) Unreliable checking for runtime dependencies

[ https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964502#comment-15964502 ] Matt Sicker commented on LOG4J2-1876: - That would be appropriate. Also, I don't think you meant to

[jira] [Commented] (LOG4J2-1867) jackson-databind dependency missing in the configuration document

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

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #62

See Changes: [mikael.staldal] LOG4J2-1867 Fix configuration documentation --

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #62

See Changes: [mikael.staldal] LOG4J2-1867 Fix configuration documentation --

[jira] [Commented] (LOG4J2-1876) Unreliable checking for runtime dependencies

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

Jenkins build is back to normal : Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #61

See - To unsubscribe, e-mail:

[jira] [Assigned] (LOG4J2-1876) Unreliable checking for runtime dependencies

[ https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1876: -- Assignee: Mikael Ståldal (was: Matt Sicker) > Unreliable checking for runtime

[jira] [Commented] (LOG4J2-1867) jackson-databind dependency missing in the configuration document

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

[jira] [Created] (LOG4J2-1877) Missing documentation for Max index limit in DefaultRolloverStrategy

chandra created LOG4J2-1877: --- Summary: Missing documentation for Max index limit in DefaultRolloverStrategy Key: LOG4J2-1877 URL: https://issues.apache.org/jira/browse/LOG4J2-1877 Project: Log4j 2

[jira] [Issue Comment Deleted] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Loman updated LOG4J2-1185: --- Comment: was deleted (was: I haven't been able to make this work in 2.8.2 (latest release as of this

[jira] [Commented] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964822#comment-15964822 ] Juan Loman commented on LOG4J2-1185: I haven't been able to make this work in 2.8.2 (latest release

[jira] [Updated] (LOG4J2-1877) Missing documentation for Max index limit in DefaultRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chandra updated LOG4J2-1877: Flags: Important Description: Guys, this is regarding the missing documentation of the max index

[jira] [Commented] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964827#comment-15964827 ] Juan Loman commented on LOG4J2-1185: I haven't been able to make this work in 2.8.2 (latest release

[jira] [Commented] (LOG4J2-1874) Add ByteBufferDestionation.write(ByteBuffer) and write(byte[], int, int) methods and call them from TextEncoderHelper whenever possible

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

[jira] [Resolved] (LOG4J2-1876) Unreliable checking for runtime dependencies

[ https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1876. Resolution: Fixed Fix Version/s: 2.9 In Git master. > Unreliable checking for

[jira] [Commented] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964923#comment-15964923 ] Juan Loman commented on LOG4J2-1185: It's still not working for me, is it because I'm using a

[jira] [Commented] (LOG4J2-1101) Date based file appender

[ https://issues.apache.org/jira/browse/LOG4J2-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964935#comment-15964935 ] Juan Loman commented on LOG4J2-1101: Nitpick: the error message {{When no file name is provided a

[Scala] Let's get version 11.0 going

I'm starting a new project at work using Scala 2.12, and I'd like to not depend on a snapshot version of the API. The maven site generates fine as far as I can tell from the Jenkins job, but I'm not sure how to appropriately integrate it into the core site. I'd like to start a release candidate

Re: [Scala] Let's get version 11.0 going

1. Perform the release build. 2. Build the site. 3. Upload the site to where we can view it. 4. Vote on it. 5. When it passes upload the site to a directory adjacent to the log4j2 site directory. Something like log4j-scala/log4j-scala-11.0. Once you have that we can modify the links in the

[jira] [Closed] (LOG4J2-239) RollingFileAppender should support logging directly to the file referenced in the filePattern.

[ https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-239. -- > RollingFileAppender should support logging directly to the file referenced in > the filePattern. >

[jira] [Resolved] (LOG4J2-239) RollingFileAppender should support logging directly to the file referenced in the filePattern.

[ https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-239. Resolution: Fixed Fix Version/s: 2.8 > RollingFileAppender should support logging directly

[jira] [Commented] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964851#comment-15964851 ] Ralph Goers commented on LOG4J2-1185: - You have to omit the fileName attribute entirely. The rolling

[jira] [Commented] (LOG4J2-239) RollingFileAppender should support logging directly to the file referenced in the filePattern.

[ https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964895#comment-15964895 ] Juan Loman commented on LOG4J2-239: --- This is solved by LOG4J2-1101 > RollingFileAppender should support

[jira] [Comment Edited] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964923#comment-15964923 ] Juan Loman edited comment on LOG4J2-1185 at 4/11/17 10:35 PM: -- It's still

[jira] [Created] (LOG4J2-1878) Dates in filename for RollingRandomAccessFile appender

Juan Loman created LOG4J2-1878: -- Summary: Dates in filename for RollingRandomAccessFile appender Key: LOG4J2-1878 URL: https://issues.apache.org/jira/browse/LOG4J2-1878 Project: Log4j 2 Issue

Jenkins build is back to normal : Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #63

See - To unsubscribe, e-mail:

org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

Hi All: Using 2.8.2, I call org.apache.logging.log4j.core.config.Configurator.initialize(String, String) with a non-exiting file location. The method does not return null because it found another log4j2.xml file on my classpath. So I get a LoggerContext but not what I expect... That does not

Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

I can see both sides of the argument. Rather than changing the semantics of the existing method, what about adding a method `Configurator.initializeStrict(String, String)` which fails if the specified file doesn't exist? Not sure what the best way to fail is: return null or throw exception...

Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

I thought Gary needed a way to detect that the specified location didn't work. But perhaps a warning message is sufficient. Sent from my iPhone > On Apr 12, 2017, at 10:05, Ralph Goers wrote: > > I'd prefer an error message but then have it continue with the

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #63

See Changes: [garydgregory] [LOG4J2-1879] Update JAnsi from 1.14 to 1.15. --

Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

I'd prefer an error message but then have it continue with the current behavior. Sent from my iPhone > On Apr 11, 2017, at 5:47 PM, Remko Popma wrote: > > I can see both sides of the argument. > > Rather than changing the semantics of the existing method, what about

[jira] [Updated] (LOG4J2-1878) Dates in filename for RollingRandomAccessFile appender

[ https://issues.apache.org/jira/browse/LOG4J2-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Loman updated LOG4J2-1878: --- Description: The feature for using dates as part of the current logfile (by omitting the filename

Re: Configuration file discovery

A better error message sounds like a good idea. If you make a Jira ticket for this, please make it part of the "ergonomics" epic: https://issues.apache.org/jira/browse/LOG4J2-1811 On Tue, Apr 11, 2017 at 9:19 PM, Mikael Ståldal wrote: > Some configuration file formats

Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

The problem with the API as it is now is that I have no idea if the API did what I asked it to do. It does initialize log4j all right but not in a way I expect. I see that we could: 1) make the current API throw an IllegalArgumentException that means "file not found", this keeps the API

[jira] [Commented] (LOG4J2-1879) Update Jansi from 1.14 to 1.15

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

[jira] [Closed] (LOG4J2-1879) Update JAnsi from 1.14 to 1.15

[ https://issues.apache.org/jira/browse/LOG4J2-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1879. Resolution: Fixed Fix Version/s: 2.9 In Git master. > Update JAnsi from 1.14 to 1.15 >

[jira] [Updated] (LOG4J2-1879) Update JAnsi from 1.14 to 1.15

[ https://issues.apache.org/jira/browse/LOG4J2-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1879: - Summary: Update JAnsi from 1.14 to 1.15 (was: Update Jansi from 1.14 to 1.15) > Update JAnsi

[jira] [Created] (LOG4J2-1879) Update Jansi from 1.14 to 1.15

Gary Gregory created LOG4J2-1879: Summary: Update Jansi from 1.14 to 1.15 Key: LOG4J2-1879 URL: https://issues.apache.org/jira/browse/LOG4J2-1879 Project: Log4j 2 Issue Type: Improvement

[jira] [Updated] (LOG4J2-1879) Update JAnsi from 1.14 to 1.15

[ https://issues.apache.org/jira/browse/LOG4J2-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1879: - Description: Update JAnsi from 1.14 to 1.15 (was: Update Jansi from 1.14 to 1.15) > Update

Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

That’s a good point. It is a programmatic interface so it should return an error. But generally we want logging to do something reasonable other than fail, so it should either use whatever configuration it finds or use the default. Ralph > On Apr 11, 2017, at 8:42 PM, Remko Popma

Wiki still mainly features 1.2

Hi All, This site could use a dust up: https://wiki.apache.org/logging-log4j Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

[jira] [Comment Edited] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964923#comment-15964923 ] Juan Loman edited comment on LOG4J2-1185 at 4/11/17 9:12 PM: - It's still not

[jira] [Created] (LOG4J2-1874) Add ByteBufferDestionation.write(ByteBuffer) and write(byte[], int, int) methods and call them from TextEncoderHelper whenever possible

Roman Leventov created LOG4J2-1874: -- Summary: Add ByteBufferDestionation.write(ByteBuffer) and write(byte[], int, int) methods and call them from TextEncoderHelper whenever possible Key: LOG4J2-1874 URL:

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963955#comment-15963955 ] Roman Leventov commented on LOG4J2-928: --- I've implemented mostly lock-free MemoryMappedFileManager.

[jira] [Commented] (LOG4J2-1874) Add ByteBufferDestionation.write(ByteBuffer) and write(byte[], int, int) methods and call them from TextEncoderHelper whenever possible

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

[jira] [Commented] (LOG4J2-1874) Add ByteBufferDestionation.write(ByteBuffer) and write(byte[], int, int) methods and call them from TextEncoderHelper whenever possible

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

[jira] [Commented] (LOG4J2-1874) Add ByteBufferDestionation.write(ByteBuffer) and write(byte[], int, int) methods and call them from TextEncoderHelper whenever possible

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

[jira] [Created] (LOG4J2-1875) Filtering Exceptions on Log4J 1.X

Mert Saygı created LOG4J2-1875: -- Summary: Filtering Exceptions on Log4J 1.X Key: LOG4J2-1875 URL: https://issues.apache.org/jira/browse/LOG4J2-1875 Project: Log4j 2 Issue Type: Request

Re: [14/14] logging-log4j2 git commit: Update BOM

OK, moved now. On Mon, Apr 10, 2017 at 6:15 PM, Ralph Goers wrote: > Yes, that is the repo. Initially, all it needs is a parent pom that > references the module you created. We can move other stuff in later. It > will need a web site of some kind but we can also

Configuration file discovery

Some configuration file formats (JSON, YAML) require additional runtime dependencies. If a such dependency is missing, configuration file location will stop and not try other configuration files with lower priority. E.g. if I have both log4j2.json and log4j2.xml in classpath, but not Jackson

Re: [14/14] logging-log4j2 git commit: Update BOM

Thanks!! Sent from my iPhone > On Apr 11, 2017, at 18:09, Mikael Ståldal wrote: > > OK, moved now. > >> On Mon, Apr 10, 2017 at 6:15 PM, Ralph Goers >> wrote: >> Yes, that is the repo. Initially, all it needs is a parent pom that >>

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #60

See Changes: [mikael.staldal] Fix Properties config examples [mikael.staldal] Fix XML config examples

[jira] [Created] (LOG4J2-1876) Unreliable checking for runtime dependencies

Mikael Ståldal created LOG4J2-1876: -- Summary: Unreliable checking for runtime dependencies Key: LOG4J2-1876 URL: https://issues.apache.org/jira/browse/LOG4J2-1876 Project: Log4j 2 Issue

[jira] [Assigned] (LOG4J2-1876) Unreliable checking for runtime dependencies

[ https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1876: -- Assignee: Mikael Ståldal > Unreliable checking for runtime dependencies >

Jenkins build is back to normal : Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #60

See - To unsubscribe, e-mail:

[jira] [Commented] (LOG4J2-1876) Unreliable checking for runtime dependencies

[ https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964296#comment-15964296 ] Mikael Ståldal commented on LOG4J2-1876: I think this can be fixed by changing

[jira] [Assigned] (LOG4J2-1876) Unreliable checking for runtime dependencies

[ https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1876: -- Assignee: Matt Sicker (was: Mikael Ståldal) > Unreliable checking for runtime

Jenkins build became unstable: Log4j 2.x #2729

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

[jira] [Resolved] (LOG4J2-1875) Filtering Exceptions on Log4J 1.X

[ https://issues.apache.org/jira/browse/LOG4J2-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1875. - Resolution: Invalid This Jira is for Log4J 2 issues only. > Filtering Exceptions on Log4J 1.X >

[jira] [Closed] (LOG4J2-1875) Filtering Exceptions on Log4J 1.X

[ https://issues.apache.org/jira/browse/LOG4J2-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1875. --- > Filtering Exceptions on Log4J 1.X > - > > Key:

[jira] [Commented] (LOG4J2-1867) jackson-databind dependency missing in the configuration document

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

[jira] [Resolved] (LOG4J2-1867) jackson-databind dependency missing in the configuration document

[ https://issues.apache.org/jira/browse/LOG4J2-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1867. Resolution: Fixed In Git master, please verify and close. > jackson-databind dependency

JSON configuration examples

There are some problems with the JSON configuration examples in the manual. I just fixed a few of them, but I still get these errors: 2017-04-11 13:45:00,954 main ERROR Route contains an invalid element or attribute "AppenderRef" 2017-04-11 13:45:00,956 main ERROR A route must specify an appender

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #59

See Changes: [mikael.staldal] Move log4j-server to Tools repo [garydgregory] Update tests from Logback 1.2.0 to 1.2.2.

[jira] [Updated] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1860: --- Fix Version/s: 2.9 > Shortcut to add Property and KeyValuePair component in

[jira] [Updated] (LOG4J2-1867) jackson-databind dependency missing in the configuration document

[ https://issues.apache.org/jira/browse/LOG4J2-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1867: --- Fix Version/s: 2.9 > jackson-databind dependency missing in the configuration document >

[jira] [Closed] (LOG4J2-1845) Handle when LogEvent.getLoggerName() returns null in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1845. -- > Handle when LogEvent.getLoggerName() returns null in KafkaAppender >

[jira] [Closed] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module

[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1851. -- > Move org.apache.logging.log4j.core.net.server package to new module >

[jira] [Assigned] (LOG4J2-1867) jackson-databind dependency missing in the configuration document

[ https://issues.apache.org/jira/browse/LOG4J2-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1867: -- Assignee: Mikael Ståldal > jackson-databind dependency missing in the configuration

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

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