[jira] [Closed] (LOG4J2-1900) Update JAnsi from 1.15 to 1.16

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

[jira] [Closed] (LOG4J2-1900) Update JAnsi from 1.15 to 1.16

[ https://issues.apache.org/jira/browse/LOG4J2-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1900. Resolution: Fixed In Git master (local build OK.) > Update JAnsi from 1.15 to 1.16 > -

[jira] [Reopened] (LOG4J2-1900) Update JAnsi from 1.15 to 1.16

[ https://issues.apache.org/jira/browse/LOG4J2-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1900: -- > Update JAnsi from 1.15 to 1.16 > -- > > Key: LOG4J2-1

[jira] [Commented] (LOG4J2-1900) Update JAnsi from 1.15 to 1.16

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

[jira] [Created] (LOG4J2-1900) Update JAnsi from 1.15 to 1.16

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

[jira] [Closed] (LOG4J2-1899) Add missing getters to classes in package org.apache.logging.log4j.core.net.ssl

[ https://issues.apache.org/jira/browse/LOG4J2-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1899. Resolution: Fixed Fix Version/s: 2.9 Already did this but worth noting in {{changes.xml}}.

[jira] [Commented] (LOG4J2-1899) Add missing getters to classes in package org.apache.logging.log4j.core.net.ssl

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

[jira] [Updated] (LOG4J2-1899) Add missing getters to classes in package org.apache.logging.log4j.core.net.ssl

[ https://issues.apache.org/jira/browse/LOG4J2-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1899: - Description: Add missing getters to classes in package {{org.apache.logging.log4j.core.net.ssl}}.

[jira] [Created] (LOG4J2-1899) Add missing getters to classes in package org.apache.logging.log4j.core.net.ssl

Gary Gregory created LOG4J2-1899: Summary: Add missing getters to classes in package org.apache.logging.log4j.core.net.ssl Key: LOG4J2-1899 URL: https://issues.apache.org/jira/browse/LOG4J2-1899 Proje

accepting self signed certificates

Hi all, I do not see a way to configure SSL with out socket appenders to accept self-signed certificates (handy if not essential during development). Am I missing something? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

[jira] [Created] (LOG4J2-1898) Update classes in org.apache.logging.log4j.core.net.ssl to the builder pattern

Gary Gregory created LOG4J2-1898: Summary: Update classes in org.apache.logging.log4j.core.net.ssl to the builder pattern Key: LOG4J2-1898 URL: https://issues.apache.org/jira/browse/LOG4J2-1898 Projec

[jira] [Commented] (LOG4J2-1896) Update org.apache.logging.log4j.core.net.ssl.StoreConfiguration from a String to char[] to represent its password

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999672#comment-15999672 ] Gary Gregory commented on LOG4J2-1896: -- All true, which leads to updating all of the

Re: WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream

On Apr 29, 2017 12:28 PM, "Gary Gregory" wrote: AFK ATM. We catch an ex and log the warning but not the ex IIRC. Yep, that is what happens. I think we might want to include the exception message but not the stacktrace. OTOH, we do not get to see nested exception messages if we did that. Gary

Re: ConfiguratonFileWatcher and co

On May 1, 2017 11:04 AM, "Gary Gregory" wrote: Thank you, I'll give it a go. Closing this thread to note that it worked. Thank you Ralph! Gary Gary On Sun, Apr 30, 2017 at 2:51 PM, Ralph Goers wrote: > If it already is monitoring files, no. You can just add your FileWatcher. > If it is n

[jira] [Reopened] (LOG4J2-1896) Update org.apache.logging.log4j.core.net.ssl.StoreConfiguration from a String to char[] to represent its password

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1896: - The implementation seems only partially complete. {{StoreConfiguration}}, {{AbstractKeyStoreConfigur

Re: Java 9, 8, 7 and Eclipse

I still do not have Eclipse working with Java 9 with our project if anyone else has any ideas... Gary On May 5, 2017 12:50 PM, "Matt Sicker" wrote: > All those compiler passes and rules and whatnot make me think that a > Makefile or Ant build would be just as simple now. :P > > On 5 May 2017 at

[GitHub] logging-log4j2 issue #74: Add a new LuceneAppender which writes logging even...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/74 How about updating the patch to provide a new module log4j-lucene5? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[jira] [Updated] (LOG4J2-1897) Implement Appender for Redis

[ https://issues.apache.org/jira/browse/LOG4J2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazıcı updated LOG4J2-1897: -- Summary: Implement Appender for Redis (was: Implement RedisAppender) > Implement Appender for

[jira] [Updated] (LOG4J2-1897) Implement RedisAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazıcı updated LOG4J2-1897: -- Description: This story aims to create a Log4j 2 NoSQL appender for Redis backends. Some highl

[jira] [Commented] (LOG4J2-1897) Implement RedisAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999566#comment-15999566 ] Volkan Yazıcı commented on LOG4J2-1897: --- [~garydgregory], makes sense, I had my fai

[jira] [Commented] (LOG4J2-1897) Implement RedisAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999562#comment-15999562 ] Gary Gregory commented on LOG4J2-1897: -- Right, the issue is not the amount of code i

Re: Log4j 2.x RedisAppender

Yeah, as mentioned on the ticket, we're working on splitting up that module as it is. On 6 May 2017 at 15:00, Gary Gregory wrote: > On Sat, May 6, 2017 at 12:48 PM, Volkan Yazıcı > wrote: > > > I was thinking of log4j-nosql Maven module. > > Cassandra, CouchDb, MongoDb appenders also exist with

Re: Log4j 2.x RedisAppender

On Sat, May 6, 2017 at 12:48 PM, Volkan Yazıcı wrote: > I was thinking of log4j-nosql Maven module. > Cassandra, CouchDb, MongoDb appenders also exist within the same Maven > module. > Are you sure that I need to create a separate Maven module just for the > Redis appender? > Let's see what othe

[jira] [Commented] (LOG4J2-1897) Implement RedisAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999559#comment-15999559 ] Matt Sicker commented on LOG4J2-1897: - We're working on splitting up our modules for

[jira] [Commented] (LOG4J2-1897) Implement RedisAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999555#comment-15999555 ] Volkan Yazıcı commented on LOG4J2-1897: --- [~garydgregory], I was thinking of {{log4j

Re: Log4j 2.x RedisAppender

Created the following JIRA ticket: LOG4J2-1897 . On Sat, May 6, 2017 at 9:06 PM, Volkan Yazıcı wrote: > Appreciated the detailed prompt reply, thanks Matt! > >1. Then I will go with Jedis without any Maven shade plugin hacks. >2. BurstFi

Re: Log4j 2.x RedisAppender

I was thinking of log4j-nosql Maven module. Cassandra, CouchDb, MongoDb appenders also exist within the same Maven module. Are you sure that I need to create a separate Maven module just for the Redis appender? On Sat, May 6, 2017 at 9:40 PM, Gary Gregory wrote: > Hi Volkan, > > Thank you for co

[jira] [Commented] (LOG4J2-1896) Update org.apache.logging.log4j.core.net.ssl.StoreConfiguration from a String to char[] to represent its password

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

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999550#comment-15999550 ] Volkan Yazıcı commented on LOG4J2-1694: --- Hey [~mikaelstaldal]! I've seen your chang

[jira] [Comment Edited] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999550#comment-15999550 ] Volkan Yazıcı edited comment on LOG4J2-1694 at 5/6/17 7:45 PM:

[jira] [Closed] (LOG4J2-1896) Update org.apache.logging.log4j.core.net.ssl.StoreConfiguration from a String to char[] to represent its password

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1896. Resolution: Fixed Fix Version/s: 2.9 In git master. > Update org.apache.logging.log4j.core.

[jira] [Commented] (LOG4J2-1897) Implement RedisAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999547#comment-15999547 ] Gary Gregory commented on LOG4J2-1897: -- This should go in a new module IMO: {{log4j-

Re: Log4j 2.x RedisAppender

Hi Volkan, Thank you for contributing to Log4j. This should do in a new Maven module IMO. Gary On Sat, May 6, 2017 at 11:30 AM, Volkan Yazıcı wrote: > Hello, > > To the best of my knowledge, there is no Redis support in Log4j 2.x NoSQL > Appenders. (Please correct if I'm wrong.) I want to cre

[jira] [Created] (LOG4J2-1897) Implement RedisAppender

Volkan Yazıcı created LOG4J2-1897: - Summary: Implement RedisAppender Key: LOG4J2-1897 URL: https://issues.apache.org/jira/browse/LOG4J2-1897 Project: Log4j 2 Issue Type: New Feature

Re: Log4j 2.x RedisAppender

The AbstractIpcAppender thing is more of a general issue that doesn't really need to be solved at this time. It's just a thought I had while thinking that SQL and NoSQL are not the only style appenders that can benefit. This could eventually be useful in refactoring the MOM appenders (JMS, Kafka, Z

Re: Log4j 2.x RedisAppender

Appreciated the detailed prompt reply, thanks Matt! 1. Then I will go with Jedis without any Maven shade plugin hacks. 2. BurstFilter covers rate limiting. 3. AsyncLogger covers consumer-producer rate mismatch regulation. 4. I've checked the CassandraAppender. It leverages the multiple

Re: Log4j 2.x RedisAppender

Instead of forming a new thread to point this out, I'll note it here: the AbstractDatabaseAppender classes may be refactorable or renamable into a sort of AbstractIpcAppender instead as another major category of appenders. Might be worth examining, though it's something we'd help in structuring at

Re: Log4j 2.x RedisAppender

Oh, I also forgot to mention that regarding batching of log messages, several appenders already follow a similar pattern, so you may find some reusable code there, especially if you're modeling this from the NoSqlAppender/Manager abstract classes as well as the AbstractDatabaseAppender/Manager clas

Re: Log4j 2.x RedisAppender

First of all, we love contributions, and this one sounds interesting, too. 1. I don't have experience with Redis (I've used other distributed memory caches and data grid frameworks, though), so I don't have an opinion on which library to use for it. 2. As for the RateLimiter class, I'll note that

Log4j 2.x RedisAppender

Hello, To the best of my knowledge, there is no Redis support in Log4j 2.x NoSQL Appenders. (Please correct if I'm wrong.) I want to create a JIRA ticket and start working on a RedisAppender. Though I do have some questions and will appreciate your feedback. 1. I plan to use Jedis