[jira] [Commented] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

[ https://issues.apache.org/jira/browse/LOG4J2-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129703#comment-16129703 ] Deepak Khobragade commented on LOG4J2-2019: --- [~ralph_go...@dslextreme.com] [~re

[jira] [Closed] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

[ https://issues.apache.org/jira/browse/LOG4J2-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2019. --- > Where does the LogEvents go when the active log file is deleted? >

[jira] [Resolved] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

[ https://issues.apache.org/jira/browse/LOG4J2-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2019. - Resolution: Invalid Fix Version/s: (was: 2.8.2) If you are running on a Unix-based sys

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

[ https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129640#comment-16129640 ] ASF GitHub Bot commented on LOG4J2-2013: Github user garydgregory commented on th

[GitHub] logging-log4j2 issue #108: LOG4J2-2013 Handle reconnect in SSLSocketManager ...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/108 Let me see if my current fix works, it needs more testing... --- 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 proje

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

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

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

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

[GitHub] logging-log4j2 issue #108: LOG4J2-2013 Handle reconnect in SSLSocketManager ...

Github user remkop commented on the issue: https://github.com/apache/logging-log4j2/pull/108 Maybe there should be a TcpSocketManagerBuilder? It could be initialized from scratch by calling its setter methods, or initialized from a TcpSocketManager instance so you'd only need to call

[jira] [Updated] (LOG4J2-2014) How to configure a Failover appender for a RollingFile Appender which is inside a RoutingAppender?

[ https://issues.apache.org/jira/browse/LOG4J2-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Khobragade updated LOG4J2-2014: -- Priority: Critical (was: Major) Issue Type: Bug (was: Question) > How to config

Re: [GitHub] logging-log4j2 issue #29: Property log4j.skipJansi should have a default of ...

I like the idea of having it as a parameter to ConsoleAppender, that would make it easy for users to find. No problem changing the default behaviour to not using Jansi. Do we still retain the current system property with its current semantics (so setting skipJansi=false would also enable colorize

[jira] [Commented] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

[ https://issues.apache.org/jira/browse/LOG4J2-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129555#comment-16129555 ] Remko Popma commented on LOG4J2-2019: - Interesting question. A simple program to repr

[jira] [Created] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

Deepak Khobragade created LOG4J2-2019: - Summary: Where does the LogEvents go when the active log file is deleted? Key: LOG4J2-2019 URL: https://issues.apache.org/jira/browse/LOG4J2-2019 Project: L

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

See

[GitHub] logging-log4j2 issue #29: Property log4j.skipJansi should have a default of ...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/29 Sure, I was just looking ahead... ;-) --- 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 this fe

[GitHub] logging-log4j2 issue #29: Property log4j.skipJansi should have a default of ...

Github user rgoers commented on the issue: https://github.com/apache/logging-log4j2/pull/29 @mikaelstaldal We have to change the default value as it can cause application startup to fail. @garydgregory I don't think it is a great loss for the status logger not to support it. --

[jira] [Commented] (LOG4J2-2002) DefaultConfigurationBuilder.writeXmlAttributes does not handle null attribute values

[ https://issues.apache.org/jira/browse/LOG4J2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129358#comment-16129358 ] Ralph Goers commented on LOG4J2-2002: - I'd have to check the code. Event if Configura

Re: [GitHub] logging-log4j2 issue #29: Property log4j.skipJansi should have a default of ...

JAnsi uses the same trick JNA uses: The native libraries it needs for each OS is embedded inside the JAR itself. At runtime, the library detects the OS and extracts the right native library from itself. Gary On Wed, Aug 16, 2017 at 1:52 PM, mikaelstaldal wrote: > Github user mikaelstaldal comme

[GitHub] logging-log4j2 issue #29: Property log4j.skipJansi should have a default of ...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/29 @garydgregory OK, maybe keep it as system property then. BTW, is there a way to safely try to load it on Windows, and gracefully do without it if the native library is missing (b

[GitHub] logging-log4j2 issue #29: Property log4j.skipJansi should have a default of ...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/29 What if we wanted to use JAnsi with the status logger? Gary On Wed, Aug 16, 2017 at 1:44 PM, Mikael Ståldal wrote: > It would quite strange to have a proper

[GitHub] logging-log4j2 issue #29: Property log4j.skipJansi should have a default of ...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/29 It would quite strange to have a property with name "skipXXX" with default value true. And it would also not be a very good idea to change default value of an existing property.

[jira] [Commented] (LOG4J2-2002) DefaultConfigurationBuilder.writeXmlAttributes does not handle null attribute values

[ https://issues.apache.org/jira/browse/LOG4J2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129307#comment-16129307 ] Mikael Ståldal commented on LOG4J2-2002: [~pburrowesOC] Can you provide some code

[jira] [Commented] (LOG4J2-2002) DefaultConfigurationBuilder.writeXmlAttributes does not handle null attribute values

[ https://issues.apache.org/jira/browse/LOG4J2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129305#comment-16129305 ] Mikael Ståldal commented on LOG4J2-2002: [~ralphgoers] Can ConfigurationBuilder c

[jira] [Assigned] (LOG4J2-2002) DefaultConfigurationBuilder.writeXmlAttributes does not handle null attribute values

[ https://issues.apache.org/jira/browse/LOG4J2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-2002: -- Assignee: Mikael Ståldal > DefaultConfigurationBuilder.writeXmlAttributes does not han

[jira] [Updated] (LOG4J2-2014) How to configure a Failover appender for a RollingFile Appender which is inside a RoutingAppender?

[ https://issues.apache.org/jira/browse/LOG4J2-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Khobragade updated LOG4J2-2014: -- Description: I am using RoutingAppender to create log files dynamically, hence inside t

[jira] [Commented] (LOG4NET-567) Use new csproj format to target multiple frameworks

[ https://issues.apache.org/jira/browse/LOG4NET-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129097#comment-16129097 ] Charles Lowell commented on LOG4NET-567: I've done this with PR [#14|https://gith

[GitHub] logging-log4net pull request #14: Add .NET Standard 2.0 build

GitHub user chlowell opened a pull request: https://github.com/apache/logging-log4net/pull/14 Add .NET Standard 2.0 build This adds a netstandard2.0 build consumable on .NET Core 2.0, .NET Framework 4.6.1+, Xamarin platforms, and the next version of UWP ([this doc](https://docs.mic

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

[ https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129047#comment-16129047 ] ASF GitHub Bot commented on LOG4J2-2013: Github user taylorp36 commented on the i

[GitHub] logging-log4j2 issue #108: LOG4J2-2013 Handle reconnect in SSLSocketManager ...

Github user taylorp36 commented on the issue: https://github.com/apache/logging-log4j2/pull/108 Yeap, the trouble I had extending TcpSocketManager was that Reconnector and Socket were both being mutated in the write() and reconnect(). Without having setters on those fields in TcpSocke

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

[ https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129018#comment-16129018 ] ASF GitHub Bot commented on LOG4J2-2013: Github user garydgregory commented on th

[GitHub] logging-log4j2 issue #108: LOG4J2-2013 Handle reconnect in SSLSocketManager ...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/108 Swamped with work ATM. I will take a look later this week, but my initial comment is the same: the duplication does not seen right. --- If your project is set up for it, you can reply

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

[ https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128998#comment-16128998 ] ASF GitHub Bot commented on LOG4J2-2013: Github user taylorp36 commented on the i

[GitHub] logging-log4j2 issue #108: LOG4J2-2013 Handle reconnect in SSLSocketManager ...

Github user taylorp36 commented on the issue: https://github.com/apache/logging-log4j2/pull/108 The code path is very similar; the tests in **org.apache.logging.log4j.core.appender.net** call the appender directly, and the test in **org.apache.logging.log4j.core.appender** applies the

[GitHub] logging-log4j2 issue #108: LOG4J2-2013 Handle reconnect in SSLSocketManager ...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/108 Please see if your new test covers a different code path from the tests I added in the **log4j-core-its** module in the package **org.apache.logging.log4j.core.appender.net**. T

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

[ https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1612#comment-1612 ] ASF GitHub Bot commented on LOG4J2-2013: Github user garydgregory commented on th

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

[ https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128844#comment-16128844 ] ASF GitHub Bot commented on LOG4J2-2013: Github user taylorp36 commented on the i

[GitHub] logging-log4j2 issue #108: LOG4J2-2013 Handle reconnect in SSLSocketManager ...

Github user taylorp36 commented on the issue: https://github.com/apache/logging-log4j2/pull/108 I added a test in the SocketAppenderTest, are there any more tests we need for this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

Jenkins build became unstable: Log4j 2.x #2993

See

[jira] [Closed] (LOG4J2-2018) LoggerNameLevelRewritePolicy documentation is wrong, example is broken

[ https://issues.apache.org/jira/browse/LOG4J2-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-2018. --- Resolution: Fixed Fixed the docs rather than the implementation. > LoggerNameLevelRewritePolicy docu

[jira] [Commented] (LOG4J2-2018) LoggerNameLevelRewritePolicy documentation is wrong, example is broken

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