Question regarding the Log4j2

Hello, I have questions regarding the use of Log4j2 here . Can I subscribe to this mailing group and ask the question here. Thanks a lot. Regards, Anhad Singh Bhasin

[jira] [Resolved] (LOG4J2-1935) Add with(String, primitive) methods to org.apache.logging.log4j.message.MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1935. -- Resolution: Fixed In git master commit 76aff58919dc5030367ea24c7c8ef42dca3b75cd > Add with(Str

[jira] [Updated] (LOG4J2-1935) Add with(String, primitive) methods to org.apache.logging.log4j.message.MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1935: - Fix Version/s: 2.9 > Add with(String, primitive) methods to > org.apache.logging.log4j.message.M

[jira] [Commented] (LOG4J2-1935) Add with(String, primitive) methods to org.apache.logging.log4j.message.MapMessage

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

[jira] [Updated] (LOG4J2-1935) Add with(String, primitive) methods to org.apache.logging.log4j.message.MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1935: - Description: Add with() methods for primitives and Object: - with(String, boolean) - with(String,

Re: [GitHub] logging-log4net issue #3: Support for types of non-parameterless constructor...

Thanks for sharing your idea. Property and ctor initialization should work together as it does in c#. Properties are set on the object that was initialized by calling the ctor. If ctor directives are missing in the xml config, the empty would be used. Similarily, an empty ctor xml config is semant

Re: [log4net] [jira] issue notifications

As far as github goes, I have muted the mirrored repository. I dont feel happy about that because I'm afraid that bumps are about to go missing. How do you handle github notifications on the logging repositories? On 8 Jun 2017 7:34 p.m., "Ralph Goers" wrote: I am all for reducing the duplicates.

Re: [log4net] [jira] issue notifications

I am all for reducing the duplicates. Ralph > On Jun 8, 2017, at 10:03 AM, Matt Sicker wrote: > > I'd definitely like to not get notified twice for tons of jira things, but > I'm not sure how to best handle that. Same goes for GitHub activity which > gets mirrored to JIRA which means sometimes

Re: [log4net] [jira] issue notifications

I'd definitely like to not get notified twice for tons of jira things, but I'm not sure how to best handle that. Same goes for GitHub activity which gets mirrored to JIRA which means sometimes I'll get 3 or 4 emails of the same message! On 8 June 2017 at 10:44, Dominik Psenner wrote: > Hi, > > c

[GitHub] logging-log4net issue #2: First version of ProcMonAppender

Github user zippy1981 commented on the issue: https://github.com/apache/logging-log4net/pull/2 This appender silently fails on windows if procmon isn't running. If I made the same thing happen on linux (probably have to do some try/catch during the interop calls) Can we include it.

[GitHub] logging-log4net issue #3: Support for types of non-parameterless constructor...

Github user jbaehr commented on the issue: https://github.com/apache/logging-log4net/pull/3 while I like the general idea, I have concerns regarding the ctor resolution. The current proposal works only with ctor arguments of type `String` and uses their names to find the right ctor. C

[log4net] [jira] issue notifications

Hi, currently jira sends issue notifications to: * all watchers * current assignee * reporter * single email address (dev@l.a.o) This puts two mails into my inbox on issues that I've picked up. Given that possible assignees are (and should anyway) all be subscribed to dev@l.a.o I would like t

[jira] [Commented] (LOG4NET-429) Pattern with Context property causes severe slowdown

[ https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042881#comment-16042881 ] ASF GitHub Bot commented on LOG4NET-429: Github user dpsenner commented on the is

[GitHub] logging-log4net issue #5: Removed the event properties in CreateCompositePro...

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/5 The patches available as attachments on issue LOG4NET-429 look more sensible to me. This patch simply removes this feature and thus breaks current behavior. In my eyes this is not a great dea

[jira] [Commented] (LOG4NET-429) Pattern with Context property causes severe slowdown

[ https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042863#comment-16042863 ] ASF GitHub Bot commented on LOG4NET-429: Github user dpsenner commented on the is

[GitHub] logging-log4net issue #5: Removed the event properties in CreateCompositePro...

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/5 There is an issue for this too (LOG4NET-429). --- 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 project does not have thi

[GitHub] logging-log4net pull request #5: Removed the event properties in CreateCompo...

GitHub user dpsenner opened a pull request: https://github.com/apache/logging-log4net/pull/5 Removed the event properties in CreateCompositeProperties In order to increase the speed up operations in almost x10 times of using properties in the output when UserName and Identity inform

[GitHub] logging-log4net issue #4: Only look at relevant log files for backup size at...

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/4 This patch can be merged into master. It lacks new test cases and therefore we should do so iff it is a stable fix and does not break existing tests. --- If your project is set up for it, yo

[GitHub] logging-log4net pull request #4: Only look at relevant log files for backup ...

GitHub user dpsenner opened a pull request: https://github.com/apache/logging-log4net/pull/4 Only look at relevant log files for backup size at initialization time. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/logging-l

[GitHub] logging-log4net issue #3: Support for types of non-parameterless constructor...

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/3 This is actually a great idea. With a few test cases this could make a great improvement. --- If your project is set up for it, you can reply to this email and have your reply appear on GitH

[GitHub] logging-log4net pull request #3: Support for types of non-parameterless cons...

GitHub user dpsenner opened a pull request: https://github.com/apache/logging-log4net/pull/3 Support for types of non-parameterless constructors in XmlConfigurator. The constructor parameters are taken from the corresponding values of the child nodes. You can add for ins

[GitHub] logging-log4net issue #2: First version of ProcMonAppender

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/2 I wonder whether we would like to have this windows specific appender in core. Do we need a separate assembly for appenders that are second class citizens? --- If your project is set up for

[GitHub] logging-log4net pull request #2: First version of ProcMonAppender

GitHub user dpsenner opened a pull request: https://github.com/apache/logging-log4net/pull/2 First version of ProcMonAppender Reopening this pull request, please discuss. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/logg

[GitHub] logging-log4net issue #1: add ColoredSmtpAppender. allow user send colorful ...

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/1 After reading this patch I think we should provide a base class that has a generic way to have customized mail messages. All the customizations (i.e. for this code the log level to color conv

[GitHub] logging-log4net pull request #1: add ColoredSmtpAppender. allow user send co...

GitHub user dpsenner opened a pull request: https://github.com/apache/logging-log4net/pull/1 add ColoredSmtpAppender. allow user send colorful log email. Opening this branch as a pull request to give us a place for discussion. You can merge this pull request into a Git repository by

[jira] [Resolved] (LOG4J2-1745) Add support for multi-release jars for JDK9+

[ https://issues.apache.org/jira/browse/LOG4J2-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1745. - Resolution: Later Going to resolve this for now as it's no longer needed at this time. Perhaps O

[jira] [Closed] (LOG4J2-1746) Add JDK9 build to Jenkins

[ https://issues.apache.org/jira/browse/LOG4J2-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-1746. --- Resolution: Delivered Agreed. Closing this as we have a sufficient implementation now thanks to the

[jira] [Updated] (LOG4J2-1828) add support for prudent mode in Log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1828: I agree, which is why we don't use that name. We have a parameter named locking. Ralph > add supp

[jira] [Commented] (LOG4J2-1675) Compile-time incompatibility regarding SimpleMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042411#comment-16042411 ] Joern Huxhorn commented on LOG4J2-1675: --- I'm fine with closing this. > Compile-tim

[jira] [Commented] (LOG4J2-1675) Compile-time incompatibility regarding SimpleMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042369#comment-16042369 ] Gary Gregory commented on LOG4J2-1675: -- It seems like the only thing to do is to doc

[jira] [Commented] (LOG4J2-1745) Add support for multi-release jars for JDK9+

[ https://issues.apache.org/jira/browse/LOG4J2-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042367#comment-16042367 ] Gary Gregory commented on LOG4J2-1745: -- Agrred. > Add support for multi-release jar

[jira] [Commented] (LOG4J2-1828) add support for prudent mode in Log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042355#comment-16042355 ] Gary Gregory commented on LOG4J2-1828: -- FWIW, "prudent mode" is a terrible name. May

Re: [log4j2] org.apache.logging.log4j.message.MapMessage String vs. Object values.

I would suggest looking at TCPSocketManager as it tries to recover from failures (although I recall seeing something saying there is a problem with the recovery losing a couple of events). Ralph > On Jun 7, 2017, at 1:11 AM, Gary Gregory wrote: > > Hi All: > > I've completed all the clean up

[jira] [Updated] (LOG4J2-1686) Add support for properties selectors

[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1686: Summary: Add support for properties selectors (was: Support conditional configuration) > Add supp

[jira] [Assigned] (LOG4J2-1686) Support conditional configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1686: --- Assignee: Ralph Goers > Support conditional configuration >