Jenkins build is still unstable: Log4j 2.x #2854

See

[jira] [Updated] (LOG4J2-1961) reconfigure breaks DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Vent updated LOG4J2-1961: --- Attachment: DirectWriteRolloverStrategy.patch I added a patch to fix the issue, including a

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

See -- Started by upstream project "log4net-trunk-build" build number 179 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment

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

See -- Started by upstream project "log4net-trunk-build" build number 178 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building

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

See -- Started by an SCM change Started by upstream project "log4net-trunk-build" build number 194 originally caused by: Started by an SCM change [EnvInject] - Loading node environment

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

See -- [...truncated 643 B...] Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in

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

See -- [...truncated 643 B...] Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in

[jira] [Updated] (LOG4J2-1908) Cryptic error message when misconfigured with File and RollingRandomAccessFile appenders targeting same file

[ https://issues.apache.org/jira/browse/LOG4J2-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1908: Description: When a configuration contains a FileAppender and a RollingRandomAccessFileAppender

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

See -- [...truncated 2.09 KB...] > git rev-parse "refs/tags/rel/1.2.9^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git rev-parse

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

See -- [...truncated 643 B...] Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in

Jenkins build is back to normal : log4net-trunk-tests #57

See

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

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: log4net-trunk-build #200

See -- Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-1 (Windows) in workspace

Build failed in Jenkins: log4net-trunk-build #176

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-3 (Windows) in workspace

Build failed in Jenkins: log4net-trunk-build #177

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-3 (Windows) in workspace

Jenkins build is back to normal : log4net-trunk-build #178

See

Build failed in Jenkins: log4net-trunk-build #193

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-3 (Windows) in workspace

Build failed in Jenkins: log4net-trunk-build #190

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-3 (Windows) in workspace

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

See -- [...truncated 643 B...] Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in

Jenkins build is back to normal : log4net-trunk-tests #64

See

Build failed in Jenkins: log4net-trunk-build #192

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-3 (Windows) in workspace

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

See -- [...truncated 3.73 KB...] http://nant.sourceforge.net Buildfile: file:///f:/jenkins/jenkins-slave/workspace/log4net-trunk-tests/log4net.build Target framework: Microsoft .NET

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

See -- Started by upstream project "log4net-trunk-build" build number 186 originally caused by: Started by an SCM change Started by an SCM change Started by upstream project

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

See -- Started by an SCM change Started by upstream project "log4net-trunk-build" build number 195 originally caused by: Started by an SCM change [EnvInject] - Loading node environment

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

See -- [...truncated 32.59 KB...] [nunit2] 11) log4net.Tests.Appender.RollingFileAppenderTest.TestInterProcessLockUnlocks : log4net.Core.LogException : Repository [TestRepository]

Build failed in Jenkins: log4net-trunk-build #184

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-3 (Windows) in workspace

Jenkins build is back to normal : log4net-trunk-build #185

See

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

See -- Started by upstream project "log4net-trunk-build" build number 196 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment

Attempting to change consumers of Log4j 2 SerializedLayout

Now when we have deprecated SerializedLayout, we should attempt to get all known consumers of it to be changed to instead/also support JsonLayout (or something else if more appropriate). The Socket Server in Log4j already support JsonLayout and XmlLayout as well, and I have just changed it to

[GitHub] logging-log4net pull request #12: This is a test whether builds.a.o picks up...

GitHub user dpsenner opened a pull request: https://github.com/apache/logging-log4net/pull/12 This is a test whether builds.a.o picks up this pull request Ideally, this build should show up at https://builds.apache.org/blue/organizations/jenkins/logging-log4net/pr You can merge

Jenkins build is back to normal : log4net-trunk-tests #75

See

Jenkins build is back to normal : log4net-trunk-build #201

See

[jira] [Commented] (LOG4J2-1908) Cryptic error message when misconfigured with File and RollingRandomAccessFile appenders targeting same file

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

Re: logging-log4j2 git commit: LOG4J2-1813 Log4j2 will now print all internal logging to the console if system property `log4j2.debug` is defined with any value (or no value).

This is great! On 30 June 2017 at 09:27, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 9d049426a -> 785892d6a > > > LOG4J2-1813 Log4j2 will now print all internal logging to the console if > system property `log4j2.debug` is defined with any

[jira] [Created] (LOG4J2-1962) Update Apache Kafka client from 0.10.2.0 to 0.11.0.0

Gary Gregory created LOG4J2-1962: Summary: Update Apache Kafka client from 0.10.2.0 to 0.11.0.0 Key: LOG4J2-1962 URL: https://issues.apache.org/jira/browse/LOG4J2-1962 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1962) Update Apache Kafka client from 0.10.2.0 to 0.11.0.0

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

[GitHub] logging-log4net pull request #12: This is a test whether builds.a.o picks up...

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4net/pull/12 --- 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

[log4net] set up basic multibranch and pull requests build

Hi, I am currently tied to my bed and used that spare time to set up basic multibranch and pull request builds that fly in from github. https://builds.apache.org/job/logging-log4net/ respectively this page: https://builds.apache.org/blue/organizations/jenkins/logging-log4net Tests and build

Re: Attempting to change consumers of Log4j 2 SerializedLayout

Chainsaw supports log4j1's xml format over UDP and TCP, as well as any regular text format via (VFS)LogFilePatternReceiver. It also supports log4j1's serialized loggingevent format. Chainsaw integration with Logj42 is via VFSLogFilePatternReceiver - you have to specify the pattern and an

Build failed in Jenkins: log4net-trunk-build #206

See Changes: [bodewig] (doc) Fix name of class LogicalThreadContext [dpsenner] Added a first jenkinsfile that does echo on a windows node. [dpsenner] Changed node to windows-2012-2 [dpsenner] Changed label

[GitHub] logging-log4net issue #12: This is a test whether builds.a.o picks up this p...

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/12 Merged with develop. --- 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

[jira] [Commented] (LOG4J2-1632) RollingRandomAccessFileAppender should be able to create files on-demand

[ https://issues.apache.org/jira/browse/LOG4J2-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070374#comment-16070374 ] Andrey Kurilov commented on LOG4J2-1632: Hi. "createOnDemand" flag is very needed in my project

[jira] [Comment Edited] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070572#comment-16070572 ] Helber Belmiro edited comment on LOG4J2-1936 at 6/30/17 6:59 PM: - [~jvz]

[jira] [Comment Edited] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070572#comment-16070572 ] Helber Belmiro edited comment on LOG4J2-1936 at 6/30/17 7:00 PM: - [~jvz]

[jira] [Commented] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070595#comment-16070595 ] Matt Sicker commented on LOG4J2-1936: - Thanks for figuring this out! Would you be able to provide a

Re: Attempting to change consumers of Log4j 2 SerializedLayout

I updated the JMS integration tests away from SerializedLayout. Gary On Fri, Jun 30, 2017 at 7:41 AM, Matt Sicker wrote: > The JMS appender supported it by default, so any configurations set up to > append to JMS and read them elsewhere as objects won't work by default >

[jira] [Commented] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070572#comment-16070572 ] Helber Belmiro commented on LOG4J2-1936: [~jvz] I've found the solution. It's necessary to change

[jira] [Commented] (LOG4J2-1858) Memory issues with ParameterizedMessage

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

Jenkins build is back to normal : log4net-trunk-build #207

See

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

See

[jira] [Closed] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[ https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1813. --- Resolution: Fixed Fix Version/s: 2.9 Fixed in master. > Provide shorter and more intuitive

Re: Attempting to change consumers of Log4j 2 SerializedLayout

The JMS appender supported it by default, so any configurations set up to append to JMS and read them elsewhere as objects won't work by default anymore, though that's somewhat a custom config more so than an application. On 30 June 2017 at 08:56, Mikael Ståldal wrote: > Now