Re: Build failed in Jenkins: Log4j 2.x #2907

Because of the ".."? Gary On Mon, Jul 17, 2017 at 10:45 PM, Ralph Goers wrote: > I suspect this is the problem: > > [DEBUG] classpathElements: [/home/jenkins/jenkins-slave/workspace/Log4j > 2.x/log4j-jmx-gui/target/classes, /home/jenkins/jenkins-slave/workspace/Log4j > 2.x/log4j-api/target/log4

[jira] [Comment Edited] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091143#comment-16091143 ] Ralph Goers edited comment on LOG4J2-1980 at 7/18/17 5:53 AM: -

[jira] [Commented] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091143#comment-16091143 ] Ralph Goers commented on LOG4J2-1980: - That would mean that weblogic.Name is not actu

Re: Build failed in Jenkins: Log4j 2.x #2907

I suspect this is the problem: [DEBUG] classpathElements: [/home/jenkins/jenkins-slave/workspace/Log4j 2.x/log4j-jmx-gui/target/classes, /home/jenkins/jenkins-slave/workspace/Log4j 2.x/log4j-api/target/log4j-api-2.9-SNAPSHOT.jar, /home/jenkins/jenkins-slave/workspace/Log4j 2.x/log4j-core/targe

[jira] [Updated] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suyog Chinche updated LOG4J2-1980: -- Environment: OS : Red Hat Enterprise Linux Server releas

[jira] [Comment Edited] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091106#comment-16091106 ] Suyog Chinche edited comment on LOG4J2-1980 at 7/18/17 4:58 AM: ---

[jira] [Comment Edited] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091106#comment-16091106 ] Suyog Chinche edited comment on LOG4J2-1980 at 7/18/17 4:57 AM: ---

[jira] [Updated] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suyog Chinche updated LOG4J2-1980: -- Description: We are using ${weblogic.Name}, which is weblogic system property used to fetch we

[jira] [Updated] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suyog Chinche updated LOG4J2-1980: -- Description: We are using $\{weblogic.Name}, which is weblogic system property used to fetch w

[jira] [Commented] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091106#comment-16091106 ] Suyog Chinche commented on LOG4J2-1980: --- Hi Ralph, Thanks for you help, We have tr

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/92 With this patch, I now get: [ERROR] Failures: [ERROR] AsyncLoggerThreadContextGarbageFreeTest>AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159->AbstractAsyncTh

Re: Build failed in Jenkins: Log4j 2.x #2907

This reminds me of how helpful your typical segmentation fault is in C++. :/ On 17 July 2017 at 21:54, Ralph Goers wrote: > > Well, this isn’t helpful. > > Ralph > > > On Jul 17, 2017, at 6:51 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > > See

Re: Build failed in Jenkins: Log4j 2.x #2907

Well, this isn’t helpful. Ralph > On Jul 17, 2017, at 6:51 PM, Apache Jenkins Server > wrote: > > See > > -- > [...truncated 13.16 MB...] > [DEBUG] Loaded System Directive: org.apache.ve

Build failed in Jenkins: Log4j 2.x #2907

See -- [...truncated 13.16 MB...] [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Break [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Evaluate [

[jira] [Updated] (LOG4J2-1977) Consider the StringBuilder's capacity instead of content length when trimming

[ https://issues.apache.org/jira/browse/LOG4J2-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1977: - External issue URL: https://github.com/apache/logging-log4j2/pull/92/ (was: https://github.com/a

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/92 Please accept my apologies, I made a mistake saying the patch was partly applied to log4j-api. It was not. The new test passes. --- If your project is set up for it, you can reply to thi

Re: Build failed in Jenkins: Log4j 2.x #2906

I am going to add -X and see if anything shows up. Ralph > On Jul 17, 2017, at 2:56 PM, Matt Sicker wrote: > > My guess would be something related to the jconsole jar as that's the only > non-standard config going on in that particular module. Could be related to > the Jenkins upgrade perhaps?

Re: Lilith and Log4j 2

Right now that is all handled by the specific layouts. For example, by default the RFC5424Layout doesn’t append newlines so when writing to a file they will all be on the same “line”, but it has an option to append one if needed. Doing the same would be another option for the JSONLayout. I’d be

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090939#comment-16090939 ] Tanner Altares commented on LOG4J2-1852: I wanted to come back here and clarify a

Re: Lilith and Log4j 2

Do we want a general event header and footer then? Gary On Jul 17, 2017 14:43, "Ralph Goers" wrote: > No. A Footer is only used at end of file. He needs to know how long each > event is or when it is the start of a new event. > > Ralph > > > On Jul 17, 2017, at 12:32 PM, Gary Gregory > wrote:

Re: Build failed in Jenkins: Log4j 2.x #2906

My guess would be something related to the jconsole jar as that's the only non-standard config going on in that particular module. Could be related to the Jenkins upgrade perhaps? I don't think I've seen this module fail locally at least with Java 8. On 17 July 2017 at 16:36, Ralph Goers wrote:

Re: Lilith and Log4j 2

From comments from Scott Deboy I believe Chainsaw also supports Log4j 2 but not in an official release. Ralph > On Jul 17, 2017, at 12:13 PM, Mikael Ståldal wrote: > > Hi. > > (Moving this discussion to logging dev mailing list.) > > Have you tried to use: > > > Then each log event will be

Re: Lilith and Log4j 2

No. A Footer is only used at end of file. He needs to know how long each event is or when it is the start of a new event. Ralph > On Jul 17, 2017, at 12:32 PM, Gary Gregory wrote: > > Can't you use a footer for any terminator you wish? > > Gary > > On Mon, Jul 17, 2017 at 12:13 PM, Mikael St

Re: Build failed in Jenkins: Log4j 2.x #2906

The log below says there was a compilation failure in jmx-gui but it doesn’t say what they were. Any ideas? Ralph > On Jul 17, 2017, at 10:44 AM, Apache Jenkins Server > wrote: > > See > > > Changes: > > [ggrego

Re: Lilith and Log4j 2

Can't you use a footer for any terminator you wish? Gary On Mon, Jul 17, 2017 at 12:13 PM, Mikael Ståldal wrote: > Hi. > > (Moving this discussion to logging dev mailing list.) > > Have you tried to use: > > > Then each log event will be terminated by end-of-line (\r\n). > > I think it would b

[jira] [Commented] (LOG4J2-1981) JsonLayout (and possibly XmlLayout and YamlLayout) should support 0-byte termination

[ https://issues.apache.org/jira/browse/LOG4J2-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090421#comment-16090421 ] Gary Gregory commented on LOG4J2-1981: -- Isn't the footer good for that? > JsonLayou

[jira] [Commented] (LOG4J2-1961) Reconfigure breaks DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090375#comment-16090375 ] Mikael Ståldal commented on LOG4J2-1961: [~cvent] Have you tried this on Java 7 o

Re: Lilith and Log4j 2

Hi. (Moving this discussion to logging dev mailing list.) Have you tried to use: Then each log event will be terminated by end-of-line (\r\n). I think it would be easy to implement 0-byte terminated log events in JsonLayout, and that would make sense since we have implemented support for th

[jira] [Created] (LOG4J2-1981) JsonLayout (and possibly XmlLayout and YamlLayout) should support 0-byte termination

Mikael Ståldal created LOG4J2-1981: -- Summary: JsonLayout (and possibly XmlLayout and YamlLayout) should support 0-byte termination Key: LOG4J2-1981 URL: https://issues.apache.org/jira/browse/LOG4J2-1981

[jira] [Commented] (LOG4J2-1311) SocketAppender will lost first serveral logs after re-connection to log servers

[ https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090319#comment-16090319 ] Dustin Koupal commented on LOG4J2-1311: --- [~jvz] That is wonderful news. Let me kno

[jira] [Commented] (LOG4J2-1311) SocketAppender will lost first serveral logs after re-connection to log servers

[ https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090312#comment-16090312 ] Matt Sicker commented on LOG4J2-1311: - [~garydgregory] has been working on a proof of

[jira] [Commented] (LOG4J2-1311) SocketAppender will lost first serveral logs after re-connection to log servers

[ https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090307#comment-16090307 ] Dustin Koupal commented on LOG4J2-1311: --- Hi [~girishkuks] did you end up coming up

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 I followed the tips to run command `mvn -U clean test -pl log4j-core -Dtest=AbstractStringLayoutTest`, and then I checked my local maven repository, but I'm afraid it didn't work. The followin

Build failed in Jenkins: Log4j 2.x #2906

See Changes: [ggregory] Fix typo in comment. -- [...truncated 1.05 MB...] [INFO] Building jar:

Re: [GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Hi, If you want your log4j-core checkout to use changes you make in log4j-api locally, then you MUST install log4j-api in your local repository (see the mvn commands I provided). BUT... In this case, the log4j-api changes are already in git master. If you want to make sure you have the latest SNA

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 After this failure, could you please check your local maven repository for the log4j-api-2.9-SNAPSHOT version, decompile the jar and check the StringBuilders class. After I got the failure, I

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/92 I have the whole project sources and all modules (sources) loaded in Eclipse so I run the one test directly from Eclipse. The commands you show will never work (did you try the

[GitHub] logging-log4j2 issue #93: modification to resolver to discover jar assests w...

Github user ta924 commented on the issue: https://github.com/apache/logging-log4j2/pull/93 Submitted code change to introduce try-with-resources block, thank you for the catch. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as w

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Agreed. I've been using 11.0-SNAPSHOT in my projects at work for a while now as it is. On 17 July 2017 at 07:39, Mikael Ståldal wrote: > Changing the artifactId would be annoying for the users who are already > using this (the Scala API has already been publicly released quite some > time ago th

[GitHub] logging-log4j2 issue #93: modification to resolver to discover jar assests w...

Github user ta924 commented on the issue: https://github.com/apache/logging-log4j2/pull/93 I will evaluate the test logic in place to see if it is an option to create a sample jar of the same structure. --- If your project is set up for it, you can reply to this email and have your r

[GitHub] logging-log4j2 pull request #93: modification to resolver to discover jar as...

Github user ta924 commented on a diff in the pull request: https://github.com/apache/logging-log4j2/pull/93#discussion_r127734669 --- Diff: log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/ResolverUtil.java --- @@ -329,6 +331,49 @@ private void loadImplem

[GitHub] logging-log4j2 pull request #93: modification to resolver to discover jar as...

Github user garydgregory commented on a diff in the pull request: https://github.com/apache/logging-log4j2/pull/93#discussion_r127726686 --- Diff: log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/ResolverUtil.java --- @@ -210,11 +210,13 @@ public void fin

[GitHub] logging-log4j2 pull request #93: modification to resolver to discover jar as...

Github user garydgregory commented on a diff in the pull request: https://github.com/apache/logging-log4j2/pull/93#discussion_r127725532 --- Diff: log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/ResolverUtil.java --- @@ -329,6 +331,49 @@ private void loa

[GitHub] logging-log4j2 pull request #93: modification to resolver to discover jar as...

Github user garydgregory commented on a diff in the pull request: https://github.com/apache/logging-log4j2/pull/93#discussion_r127725284 --- Diff: log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/ResolverUtil.java --- @@ -210,11 +210,13 @@ public void fin

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089889#comment-16089889 ] Tanner Altares commented on LOG4J2-1852: PR https://github.com/apache/logging-log

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089887#comment-16089887 ] ASF GitHub Bot commented on LOG4J2-1852: GitHub user ta924 opened a pull request:

[GitHub] logging-log4j2 pull request #93: modification to resolver to discover jar as...

GitHub user ta924 opened a pull request: https://github.com/apache/logging-log4j2/pull/93 modification to resolver to discover jar assests without the manipula… …tion of asset paths. This PR is to address issue https://issues.apache.org/jira/browse/LOG4J2-1852. If the

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 I reappeared the failure! when I run the tests with `mvn clean test -pl log4j2-core`, I got the following failure (it is just the failure you provided) ``` [ERROR] Failures: [

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Changing the artifactId would be annoying for the users who are already using this (the Scala API has already been publicly released quite some time ago through the main repo). I don't like that. On 2017-07-16 23:04, Ralph Goers wrote: To address Gary’s issues I think it would be better to us

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Can't we just go on with what we decieded months ago? I think it's a bit late to change it now, and everyone has have the oppourtnity to discuss this for a long time. On 2017-07-16 23:04, Ralph Goers wrote: To address Gary’s issues I think it would be better to use a different module name an

[jira] [Commented] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089748#comment-16089748 ] Ralph Goers commented on LOG4J2-1980: - If it is a system property it should be specif

[jira] [Updated] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suyog Chinche updated LOG4J2-1980: -- Description: We are using ${weblogic.Name}, which is weblogic system property used to fetch we

JDK 9 EA Build 178 & JDK 8u152 b05 are available on jdk.java.net

Hi Nick, *JDK 9 Early Access* build 178 is available at : - jdk.java.net/9/ A summary of all the changes in this build are listed here . Changes which were introduced since the last availability email that may be of interest : *

[jira] [Updated] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suyog Chinche updated LOG4J2-1980: -- Summary: log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[jira] [Updated] (LOG4J2-1980) log4j2.xml property substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suyog Chinche updated LOG4J2-1980: -- Description: We are using ${weblogic.Name}, which is weblogic system property used to fetch we

[jira] [Created] (LOG4J2-1980) log4j2.xml property substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

Suyog Chinche created LOG4J2-1980: - Summary: log4j2.xml property substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3 Key: LOG4J2-1980 URL: https://issues.apache.org/jira/browse/LOG4J2-1980

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089643#comment-16089643 ] Tanner Altares commented on LOG4J2-1852: I can work on submitting a patch this we

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089434#comment-16089434 ] Maksym Novoseltsev commented on LOG4J2-1852: Hi [~garydgregory], unfortunatel

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 I merged the latest master to my branch just now, Would you please run the case again, and show me the result? @garydgregory --- If your project is set up for it, you can reply to this email

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 Still reports this problem? Hmm... interesting. I also have ran this case in my IDE, nothing went wrong. Would you please show me the git repository version, maybe we have to check if we are r