[jira] [Resolved] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

[ https://issues.apache.org/jira/browse/LOGCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-489. -- Resolution: Fixed Fix Version/s: 0.11.0 This sounds exactly like already reported

Jenkins build became unstable: Log4j 2.x #2867

See

[jira] [Resolved] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile

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

[jira] [Commented] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile

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

[jira] [Commented] (LOG4J2-1725) RollingFileAppender's filePattern not reloaded when using monitorInterval

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

[GitHub] logging-log4j2 pull request #90: [LOG4J2-1725] RollingFileAppender's filePat...

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/90 --- 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 feature enabled and wishes so, or if the feature

[jira] [Updated] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1964: - Summary: Dynamic reconfiguration does not work for filePattern of RollingFile (was: Dynamic conf

[jira] [Updated] (LOG4J2-1964) Dynamic configuration does not work for filePattern of RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1964: - Summary: Dynamic configuration does not work for filePattern of RollingFile (was: dynamic config

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

See

Jenkins build is unstable: Log4j 2.x #2865

See

[jira] [Resolved] (LOG4J2-1955) JMS Appender should be able connect to a broker (later) even it is not present at configuration time

[ https://issues.apache.org/jira/browse/LOG4J2-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1955. -- Resolution: Fixed Fix Version/s: 2.9 In Git master. Recoded to follow the Reconnect thre

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075723#comment-16075723 ] Gary Gregory commented on LOG4J2-1934: -- In Git master: Recoded to follow the Reconne

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

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

[jira] [Commented] (LOG4J2-1955) JMS Appender should be able connect to a broker (later) even it is not present at configuration time

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

Build failed in Jenkins: Log4j 2.x #2864

See Changes: [ggregory] Use try-with-resources instead of closing in a finally block. -- [...truncated 1.11 MB...] at org.apache.avro.ipc.Requestor.writeHandshake(Reque

[jira] [Updated] (LOG4J2-1955) JMS Appender should be able connect to a broker (later) even it is not present at configuration time

[ https://issues.apache.org/jira/browse/LOG4J2-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1955: - Description: JMS Appender should be able connect to a broker (later) even it is not present at c

[jira] [Updated] (LOG4J2-1955) JMS Appender should be able connect to a broker (later) even it is not present at configuration time

[ https://issues.apache.org/jira/browse/LOG4J2-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1955: - Summary: JMS Appender should be able connect to a broker (later) even it is not present at config

[jira] [Updated] (LOG4J2-1955) JMS Appender should be able connect to a broker (later) even it is not present at configuration time.

[ https://issues.apache.org/jira/browse/LOG4J2-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1955: - Summary: JMS Appender should be able connect to a broker (later) even it is not present at config

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user remkop commented on the issue: https://github.com/apache/logging-log4j2/pull/87 I don't have access to hardware with that version of Java. I am fairly sure that 131 doesn't have performance improvements (we checked whether we should upgrade but it was too close to our go-l

[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&focusedCommentId=16075588#comment-16075588 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user remkop commented on the issue:

Re: [Log4j] release 2.9

So 11.0 would have the old name, and 12.0 would have the new name? That would be fine with me. That also gives us an opportunity to look into Scalameta for simpler macro portability going forward considering I keep seeing deprecation warnings all over the place in the existing macro API. On 5 July

Re: [Log4j] Android support

A minimal log4j-android-core type of thing could be handy, though I feel that would be easier to do with the log4j-core modularization I proposed a while back. We wouldn't want to duplicate plugin code and things like that. On 5 July 2017 at 15:57, Mikael Ståldal wrote: > It would also be good i

Re: [Log4j] Android support

It would also be good if log4j-jul works on Android. And log4j-jcl (given that commons-logging itself works). And log4j-slf4j-impl and log4j-to-slf4j (given that SLF4J itself works). On 2017-07-05 22:19, Mikael Ståldal wrote: I think it is enough with log4j-api support for Android in the 2.9

[jira] [Updated] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

[ https://issues.apache.org/jira/browse/LOGCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Heath updated LOGCXX-489: --- Description: Attempting to build log4cxx 0.10.0 from source fails on make with the following error on

[jira] [Updated] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

[ https://issues.apache.org/jira/browse/LOGCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Heath updated LOGCXX-489: --- Description: Attempting to build log4cxx 0.10.0 from source fails with the following error on CentOS

[jira] [Updated] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

[ https://issues.apache.org/jira/browse/LOGCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Heath updated LOGCXX-489: --- Description: Attempting to build log4cxx 0.10.0 from source fails with the following error on CentOS

[jira] [Created] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

Simon Heath created LOGCXX-489: -- Summary: log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope Key: LOGCXX-489 URL: https://issues.apache.org/jira/browse/LOGCXX-489

Re: [Log4j] Android support

I think it is enough with log4j-api support for Android in the 2.9 release, we can fix log4j-core (or provide an alternative) later. On 2017-07-05 22:05, Mikael Ståldal wrote: First of all, we need to make sure that at least log4j-api works flawlessy on Android. I think this is already covered

Re: [Log4j] release 2.9

But this long package name is already out released for Scala 2.10 and 2.11. I suggest we release for 2.12 with the same package name, and then maybe change it in the next release. On 2017-07-05 22:10, Matt Sicker wrote: I've been using the 2.12 snapshot for now, but I'd rather get a released

Re: [Log4j] release 2.9

I've been using the 2.12 snapshot for now, but I'd rather get a released solution. I have one thought that our package name in the Scala API is too long as most Scala libraries I've used do not use the reverse DNS package naming scheme. We may be better off renaming it to just log4j as the root pac

[Log4j] Android support

First of all, we need to make sure that at least log4j-api works flawlessy on Android. I think this is already covered by LOG4J2-1926. But do we also aim for having log4j-core working on Android? It seems to me that it could be a lot of work (and possibly force us to remove some Android-incomp

[jira] [Updated] (LOG4J2-460) java.lang.ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-460: -- Labels: Android (was: Andriod) > java.lang.ClassCastException: > org.apache.logging.log4j.simp

[jira] [Updated] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1921: --- Labels: Android (was: Andriod) > Getting ClassCastException while getting LoggerContext > --

[jira] [Updated] (LOG4J2-728) Look for log4j2.xml in assets folder (or the application data) in an Android APK.

[ https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-728: -- Labels: Android (was: Andriod) > Look for log4j2.xml in assets folder (or the application data)

[jira] [Updated] (LOG4J2-719) Android throws NetworkOnMainThreadException during Log4j2 initialization

[ https://issues.apache.org/jira/browse/LOG4J2-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-719: -- Labels: Android (was: Andriod) > Android throws NetworkOnMainThreadException during Log4j2 init

[jira] [Updated] (LOG4J2-716) Auto-disable JMX when detecting Android

[ https://issues.apache.org/jira/browse/LOG4J2-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-716: -- Labels: Android (was: Andriod) > Auto-disable JMX when detecting Android >

[jira] [Updated] (LOG4J2-1915) Log4j2 version 2.8.2 is not working for android logging

[ https://issues.apache.org/jira/browse/LOG4J2-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1915: --- Labels: Android (was: Andriod) > Log4j2 version 2.8.2 is not working for android logging Ha

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075316#comment-16075316 ] Mikael Ståldal commented on LOG4J2-1921: Is this a duplicate of https://issues.ap

[jira] [Updated] (LOG4J2-460) java.lang.ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-460: -- Labels: Andriod (was: ) > java.lang.ClassCastException: > org.apache.logging.log4j.simple.Simp

[jira] [Updated] (LOG4J2-716) Auto-disable JMX when detecting Android

[ https://issues.apache.org/jira/browse/LOG4J2-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-716: -- Labels: Andriod (was: ) > Auto-disable JMX when detecting Android > ---

[jira] [Updated] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1921: --- Labels: Andriod (was: ) > Getting ClassCastException while getting LoggerContext > -

[jira] [Updated] (LOG4J2-713) Android: java.lang.VerifyError: org/apache/logging/log4j/core/util/Closer

[ https://issues.apache.org/jira/browse/LOG4J2-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-713: -- Labels: Android (was: ) > Android: java.lang.VerifyError: org/apache/logging/log4j/core/util/Cl

[jira] [Updated] (LOG4J2-728) Look for log4j2.xml in assets folder (or the application data) in an Android APK.

[ https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-728: -- Labels: Andriod (was: android) > Look for log4j2.xml in assets folder (or the application data)

[jira] [Updated] (LOG4J2-719) Android throws NetworkOnMainThreadException during Log4j2 initialization

[ https://issues.apache.org/jira/browse/LOG4J2-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-719: -- Labels: Andriod (was: ) > Android throws NetworkOnMainThreadException during Log4j2 initializat

[jira] [Updated] (LOG4J2-703) Android: Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-703: -- Labels: Android (was: ) > Android: Could not find class 'javax.naming.InitialContext', referenc

[jira] [Updated] (LOG4J2-1915) Log4j2 version 2.8.2 is not working for android logging

[ https://issues.apache.org/jira/browse/LOG4J2-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1915: --- Labels: Andriod (was: ) > Log4j2 version 2.8.2 is not working for android logging Happens i

Re: HttpAppenderTest fails randomly and often

I don't know where to start, so you have to test and debug a bit so that we know why it fails. First we need to know if the JVM crash or just exit normally (but unexpected). On 2017-07-05 21:31, Gary Gregory wrote: I can test if you want to throw patches-PRs over the wall... Gary On Jul 5, 2

Re: HttpAppenderTest fails randomly and often

I can test if you want to throw patches-PRs over the wall... Gary On Jul 5, 2017 12:19, "Mikael Ståldal" wrote: > It seems like I don't really have easy access to any Windows machine. > > > On 2017-06-16 21:49, Gary Gregory wrote: > >> Would you mind putting that on your todo list? >> >> Thank

Re: [Log4j] release 2.9

An important customer for us is Apache HttpClient for which I already switched to Log4j2 in the 5.0 (alpha level) branch. I am on the PMC there as well. Any help to get Android cooking for Log4j modules would be g r e a t. I am on deadline at work until the end of the month so my time is limited an

Re: HttpAppenderTest fails randomly and often

It seems like I don't really have easy access to any Windows machine. On 2017-06-16 21:49, Gary Gregory wrote: Would you mind putting that on your todo list? Thank you? Gary On Jun 16, 2017 11:19 AM, "Mikael Ståldal" wrote: No, not right now. On 2017-06-16 21:17, Gary Gregory wrote: On

Re: [Log4j] release 2.9

There are a couple of almost finished PRs on GitHub which would be nice to include. I'll have a look at LOG4J2-1923 (PR #81) in the comming days. It would be good to do something about LOG4J2-1921 (Android support). I guess it boils down to what level of support for Android we want. Is it enou

[jira] [Closed] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1587. -- > Build process should work on Java 8 > --- > > Key

[jira] [Updated] (LOG4J2-1923) JSONLayout should allow stacktrace as string

[ https://issues.apache.org/jira/browse/LOG4J2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1923: --- Affects Version/s: 2.8.2 > JSONLayout should allow stacktrace as string > ---

[jira] [Assigned] (LOG4J2-1923) JSONLayout should allow stacktrace as string

[ https://issues.apache.org/jira/browse/LOG4J2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1923: -- Assignee: Mikael Ståldal > JSONLayout should allow stacktrace as string >

Build failed in Jenkins: logging-log4net » PR-4 #8

See -- [...truncated 12.93 KB...] set-net-3.5-runtime-configuration: check-log4net-basedir: check-current-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\wor

Build failed in Jenkins: logging-log4net » PR-1 #8

See -- [...truncated 933 B...] Fetching upstream changes from https://github.com/apache/logging-log4net.git using GIT_ASKPASS to set credentials dpsenner at github > git fetch --tag

Build failed in Jenkins: logging-log4net » PR-8 #8

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: logging-log4net » PR-3 #8

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: logging-log4net » PR-2 #8

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: log4net-trunk-tests #107

See Changes: [dpsenner] Jenkinsfile: net-standard export /home/jenkins instead of /home -- Started by upstream project "log4net-trunk-build" build number 237 originally

[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&focusedCommentId=16075093#comment-16075093 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user garydgregory commented on the i

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/87 Thank you for running the benchmarks. Is this worth doing over on the _current_ Java 8 runtime (_131)? Gary On Wed, Jul 5, 2017 at 6:59 AM, Remko Popma wrote:

[jira] [Closed] (LOG4J2-1968) GelfLayout/SocketAppender does document "includeNullDelimiter" to append the frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1968. Resolution: Duplicate Fix Version/s: 2.9 This issue is a duplicate of [LOG4J2-1854]. Please

[jira] [Resolved] (LOG4J2-1968) GelfLayout/SocketAppender does document "includeNullDelimiter" to append the frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1968. -- Resolution: Fixed > GelfLayout/SocketAppender does document "includeNullDelimiter" to append th

[jira] [Reopened] (LOG4J2-1968) GelfLayout/SocketAppender does document "includeNullDelimiter" to append the frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1968: -- > GelfLayout/SocketAppender does document "includeNullDelimiter" to append the > frame delimiter n

[jira] [Updated] (LOG4J2-1968) GelfLayout/SocketAppender does document "includeNullDelimiter" to append the frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1968: - Summary: GelfLayout/SocketAppender does document "includeNullDelimiter" to append the frame delim

[jira] [Updated] (LOG4J2-1968) GelfLayout/SocketAppender does document how to append the frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1968: - Affects Version/s: 2.8.2 > GelfLayout/SocketAppender does document how to append the frame delimi

[jira] [Updated] (LOG4J2-1968) GelfLayout/SocketAppender does document how to append the frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1968: - Summary: GelfLayout/SocketAppender does document how to append the frame delimiter null byte when

[jira] [Comment Edited] (LOG4J2-1968) GelfLayout/SocketAppender does not append frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075083#comment-16075083 ] Gary Gregory edited comment on LOG4J2-1968 at 7/5/17 5:01 PM: -

[jira] [Commented] (LOG4J2-1968) GelfLayout/SocketAppender does not append frame delimiter null byte when using TCP

[ https://issues.apache.org/jira/browse/LOG4J2-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075083#comment-16075083 ] Gary Gregory commented on LOG4J2-1968: -- Please use {{includeNullDelimiter="true"}} i

[jira] [Closed] (LOG4J2-1966) Include separator option of PatternLayout in manual (and other updates)

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1966. Closing per user comment. > Include separator option of PatternLayout in manual (and other updates) >

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #56

thanks dominik, that’d be of great help! I don’t mind getting updates on regular builds(success) and occasional failures — if any. But, as I understand the build pipeline is/was broken. And this was filling up my mailbox. Since, I have a limited quota. I was concerned. thanks for your quick fix

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #56

Hi, I'm currently in the process of writing the build pipeline for log4net. During this process errors will continue to pop up and I understand that people don't want to be nagged. Therefore I've just pushed a change to send mails to commit@ instead. This way I can examine them and continue my wor

[GitHub] logging-log4j2 issue #91: failing test - irregular log4j2.json nodes order

Github user rgoers commented on the issue: https://github.com/apache/logging-log4j2/pull/91 After a bunch of interesting reading it appears that ES2015 says that Object property names are to be ordered in the following way: integer-like Strings in ascending order, non-integer-like Str

[GitHub] logging-log4j2 issue #91: failing test - irregular log4j2.json nodes order

Github user waymirec commented on the issue: https://github.com/apache/logging-log4j2/pull/91 After a bunch of interesting reading it appears that ES2015 says that Object property names are to be ordered in the following way: integer-like Strings in ascending order, non-integer-like

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #56

hi, this is my 2nd reminder. this has become a regular,  I see my mailbox full of build failure emails. Isn’t there anyone responsible suppressing this? — I’d be force to unsubscribe, for the love of god, please handle this! thanks,Chandra On 5 Jul 2017, 8:56 PM +0530, Apache Jenkins Server ,

Re: [Log4j] release 2.9

I'd be alright with that. We'll just have to push back some goals to 2.10. I have an outstanding properties change I want to merge, but I don't have time at the moment to go through and make all the documentation updates it requires, so I can push that for 2.10. Same goes for the Scala repo since I

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #56

See -- [...truncated 80.28 KB...] set-debug-build-configuration: check-current-build-config: set-build-configuration-flags: compile-mono-2.0-current-config

Build failed in Jenkins: logging-log4net » feature/RollingFileAppender-NG #5

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Obtained Jenkinsfile from e33ab6cfc96b81261430cc

Build failed in Jenkins: logging-log4net » PR-2 #7

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: logging-log4net » PR-3 #7

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: logging-log4net » PR-4 #7

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: logging-log4net » PR-1 #7

See -- [...truncated 1.13 KB...] Merging develop commit 3cd1743c5eecbe62d48c6cc698384dce4c2782b4 into PR head commit 3c930d8d9b35cbfe1ba3e7ad93ff888d71f94f01 > git config core.spar

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #44

Hi It was tough, but after all i was able to solve the above issues by reading the source code of the plugins involved. Yes, the documentation is that poor. 1. we make use of xunit to process nunit test results 2. i was able to allow test to not abort the build by editing tests/nant.build as foll

Build failed in Jenkins: log4net-trunk-tests #106

See Changes: [dpsenner] netstandard: added docker machine that can build netstandard and [dpsenner] Jenkinsfile: added stage that builds dotnet-standard [dpsenner] Jenkinsfile: fixed syntax typo [dpsenner] J

[jira] [Commented] (LOG4J2-1967) Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074829#comment-16074829 ] Paul K commented on LOG4J2-1967: yes, I do set the property using below: String

[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&focusedCommentId=16074802#comment-16074802 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user remkop commented on the issue:

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user remkop commented on the issue: https://github.com/apache/logging-log4j2/pull/87 As promised, here are the throughput results on enterprise hardware. Hardware: total 64 cores (4x 16-core) Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz Java Hotspot 64-bit server 1.8.

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #49

See -- [...truncated 129.12 KB...] set-build-configuration-flags: compile-netstandard-current-configuration: [exec] /usr/share/dotnet/sdk/1.0.4/NuGet.tar

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #48

See -- [...truncated 9.49 KB...] check-current-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\workspace\log4net_feature_cd-pipeline-76KUCPOD

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #47

See -- [...truncated 9.46 KB...] check-current-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\workspace\log4net_feature_cd-pipeline-76KUCP

[GitHub] logging-log4j2 issue #91: failing test - irregular log4j2.json nodes order

Github user romanso123 commented on the issue: https://github.com/apache/logging-log4j2/pull/91 Yea, saw that. But still... in general, a JSON is not supposed to have order.. In my opinion this design is flawed. Anyway you decide what to do with it. Thanks. --- If

[jira] [Created] (LOG4J2-1968) GelfLayout/SocketAppender does not append frame delimiter null byte when using TCP

Peter Lauko created LOG4J2-1968: --- Summary: GelfLayout/SocketAppender does not append frame delimiter null byte when using TCP Key: LOG4J2-1968 URL: https://issues.apache.org/jira/browse/LOG4J2-1968 Proj

[jira] [Updated] (LOG4J2-1912) CompositeConfiguration: Unable to determine URI for configuration. However, the reconfiguration is completed.

[ https://issues.apache.org/jira/browse/LOG4J2-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] R Ri updated LOG4J2-1912: - Priority: Major (was: Trivial) > CompositeConfiguration: Unable to determine URI for configuration. However, >

[GitHub] logging-log4j2 issue #91: failing test - irregular log4j2.json nodes order

Github user jochenw commented on the issue: https://github.com/apache/logging-log4j2/pull/91 Quoting Ralph Goers: This is not a bug but is intentional. Log4j processes configuration files from beginning to end. It does not scan the file twice as would be necessary if no order

[jira] [Commented] (LOG4J2-1966) Include separator option of PatternLayout in manual (and other updates)

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074477#comment-16074477 ] M Sazzadul Hoque commented on LOG4J2-1966: -- I checked and it seems OK to me. >