[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=16091143#comment-16091143 ] Ralph Goers edited comment on LOG4J2-1980 at 7/18/17 5:53 AM: -- That would

[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=16091143#comment-16091143 ] Ralph Goers commented on LOG4J2-1980: - That would mean that weblogic.Name is not actually a system

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

[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

[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=16091106#comment-16091106 ] Suyog Chinche edited comment on LOG4J2-1980 at 7/18/17 4:58 AM: Hi Ralph,

[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

[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]

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: > > > >

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

[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:

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

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,

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 >

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). > >

[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=16090319#comment-16090319 ] Dustin Koupal commented on LOG4J2-1311: --- [~jvz] That is wonderful news. Let me know if I can help

[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=16090312#comment-16090312 ] Matt Sicker commented on LOG4J2-1311: - [~garydgregory] has been working on a proof of concept for

[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=16090307#comment-16090307 ] Dustin Koupal commented on LOG4J2-1311: --- Hi [~girishkuks] did you end up coming up with a way to

[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

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

[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

[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

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

[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

[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

[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=16089889#comment-16089889 ] Tanner Altares commented on LOG4J2-1852: PR https://github.com/apache/logging-log4j2/pull/93 has

[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

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

[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=16089748#comment-16089748 ] Ralph Goers commented on LOG4J2-1980: - If it is a system property it should be specified as

[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

[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

[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=16089643#comment-16089643 ] Tanner Altares commented on LOG4J2-1852: I can work on submitting a patch this week.

[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=16089434#comment-16089434 ] Maksym Novoseltsev commented on LOG4J2-1852: Hi [~garydgregory], unfortunately, I am not in a

[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

[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

Re: [Log4j] Lucene 5 Appender

It is fine as long as it is documented that it can and why. Ralph > On Jul 16, 2017, at 11:22 PM, Gary Gregory wrote: > > On Sun, Jul 16, 2017 at 11:20 PM, Ralph Goers > wrote: > >> If there is no split then events could be lost during a

Re: [Log4j] Lucene 5 Appender

I should add that it isn’t very likely though. Ralph > On Jul 16, 2017, at 11:20 PM, Ralph Goers wrote: > > If there is no split then events could be lost during a reconfigure. > > Ralph > >> On Jul 16, 2017, at 11:18 PM, Gary Gregory

Re: [Log4j] Lucene 5 Appender

If there is no split then events could be lost during a reconfigure. Ralph > On Jul 16, 2017, at 11:18 PM, Gary Gregory wrote: > > Hi All: > > I have a Lucene5 branch based on a patch from a user which said user has in > production. > > The only obvious failing I see

[Log4j] Lucene 5 Appender

Hi All: I have a Lucene5 branch based on a patch from a user which said user has in production. The only obvious failing I see is that there is no split between appender and manager. The manager split could be done later. I am wondering if anyone has time to code review the branch. Thank you,