[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=16095822#comment-16095822 ] Ajitha commented on LOG4J2-1921: Ok, I am rewritting my implementation and checking. Shal

[GitHub] logging-log4j2 pull request #95: Kpm1985

GitHub user kpm1985 opened a pull request: https://github.com/apache/logging-log4j2/pull/95 Kpm1985 I have cleaned up a few files and removed empty comments. The default buffer size in certain implementations was 8102, which I believe was a typo because 8192 is a power of two. Toda

[jira] [Commented] (LOG4J2-1983) Scala API does not work with IBM Java 8 and Scala 2.12

[ https://issues.apache.org/jira/browse/LOG4J2-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095745#comment-16095745 ] Gary Gregory commented on LOG4J2-1983: -- My crash data: https://pastebin.com/Lgq98MjF

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

Logged internally: https://issues.apache.org/jira/browse/LOG4J2-1983 On 20 July 2017 at 22:22, Matt Sicker wrote: > I did find this Scala issue: https://github.com/scala/bug/issues/10417 > > On 20 July 2017 at 22:07, Gary Gregory wrote: > >> On Thu, Jul 20, 2017 at 7:22 PM, Matt Sicker wrote:

[jira] [Created] (LOG4J2-1983) Scala API does not work with IBM Java 8 and Scala 2.12

Matt Sicker created LOG4J2-1983: --- Summary: Scala API does not work with IBM Java 8 and Scala 2.12 Key: LOG4J2-1983 URL: https://issues.apache.org/jira/browse/LOG4J2-1983 Project: Log4j 2 Issue

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

I did find this Scala issue: https://github.com/scala/bug/issues/10417 On 20 July 2017 at 22:07, Gary Gregory wrote: > On Thu, Jul 20, 2017 at 7:22 PM, Matt Sicker wrote: > > > As for the 2.12 IBM JDK bug, could be worth filing a jira ticket over it. > > > > Creating a JIRA/issue where though?

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

That would probably help, though I meant tracking it in our jira. Unless you think we should try to fix this or find a root cause before releasing 11.0. I'm not sure if IBM JDK is compatible with Scala 2.12 in the first place, so it might be a bug on their end. On 20 July 2017 at 22:07, Gary Grego

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

On Thu, Jul 20, 2017 at 7:22 PM, Matt Sicker wrote: > As for the 2.12 IBM JDK bug, could be worth filing a jira ticket over it. > Creating a JIRA/issue where though? In IBM's system? Gary > Since they don't seem to publish the IBM JDK for macOS, that may make it > harder to test a fix, but we

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

On Thu, Jul 20, 2017 at 7:35 PM, Matt Sicker wrote: > I looked into this a bit more. If we made a 2.13 release now, we'd have to > name the module more specifically. In this case, it'd be > "log4j-api-scala_2.13.0-M1". The version number in the module name can be > as specific as the exact compil

Re: [log4j2] sys props driving me nuts

On Thu, Jul 20, 2017 at 7:19 PM, Matt Sicker wrote: > I haven't been able to get to this so far this week. Been finishing up a > project for work. I should hopefully have enough time to merge this > tomorrow though. > Thank you for the update Matt. Gary > > On 16 July 2017 at 14:36, Gary Greg

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

I looked into this a bit more. If we made a 2.13 release now, we'd have to name the module more specifically. In this case, it'd be "log4j-api-scala_2.13.0-M1". The version number in the module name can be as specific as the exact compiler version (which is more important for compiler plugins than

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

As for the 2.12 IBM JDK bug, could be worth filing a jira ticket over it. Since they don't seem to publish the IBM JDK for macOS, that may make it harder to test a fix, but we can possibly make a Dockerfile for it. On 20 July 2017 at 21:18, Matt Sicker wrote: > To test for 2.13.0, we'd need to m

Re: [log4j2] sys props driving me nuts

I haven't been able to get to this so far this week. Been finishing up a project for work. I should hopefully have enough time to merge this tomorrow though. On 16 July 2017 at 14:36, Gary Gregory wrote: > On Sun, Jul 16, 2017 at 12:29 PM, Matt Sicker wrote: > > > I don't think I'll have time t

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

To test for 2.13.0, we'd need to make a 2.13.0 jar for log4j-api-scala. You can try it out by either copying or modifying the 2.12 one and changing the compiler version. Using sbt, it's a bit easier to cross compile various versions (future goal in this repo). I'm not sure if it's such a great idea

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

HI Matt, - 2.10.6 Hello, world! - 2.11.8 Hello, world! - 2.11.11 Hello, world! - 2.12.1 crashes - 2.12.0 crashes How do I update the sbt file to test 2.13.0-M1? Gary On Thu, Jul 20, 2017 at 6:27 PM, Matt Sicker wrote: > Can you try changing the Scala version in build.sbt to

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

Can you try changing the Scala version in build.sbt to 2.11.8 or 2.10.6? Those only require Java 6 btw. On 20 July 2017 at 16:58, Gary Gregory wrote: > Here is the JVM dump, not that we can do anything about it! :-P > > https://gist.githubusercontent.com/garydgregory/ > 1e8d78d6305fe5379efccf76f

Fwd: Review Request 61010: HIVE-17128 Operation Logging leaks file descriptors as the log4j Appender is never closed

In the Apache Hive message below, you'll see mention of using reflection to implement something I thought we already supported: closing files file that are dynamically created. Any thoughts on how set get Hive to use Log4j in a safer manner? Gary -- Forwarded message -- From: Aih

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

Here is the JVM dump, not that we can do anything about it! :-P https://gist.githubusercontent.com/garydgregory/1e8d78d6305fe5379efccf76fadf0b25/raw/1411977cea9a14328f17ff99f35bfc951c1eb1c0/javacore.20170720.133045.13856.0004.txt Gary On Thu, Jul 20, 2017 at 2:53 PM, Gary Gregory wrote: > In i

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

In installed SBT and ran: 'sbt clean run' and it hangs hard with IBM Java, CTRL-C does nothing: https://pastebin.com/HWYniJXB Gary On Thu, Jul 20, 2017 at 1:25 PM, Matt Sicker wrote: > The sbt script is just added for convenience in case you don't have sbt > installed already. Regardless, sbt h

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

See

Re: [Log4j] includeNullDelimiter

I'm not a fan of the null termination as it is. Do you know how many millions or billions of dollars have been wasted due to buggy C and C++ programs thanks to null-terminated strings? Almost as bad as null itself. ;) Having some way to delimit log events could be handy later on for garbage-free n

Re: [Log4j] log4j-server

Is the repo ready for release? I can probably be the RM for it. These smaller modules take quite a bit less time to make RCs for than the main repo (which is why we're working on splitting it up in the first place). On 20 July 2017 at 14:48, Mikael Ståldal wrote: > The SocketServer stuff is now

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

The sbt script is just added for convenience in case you don't have sbt installed already. Regardless, sbt has to download itself as it is similar to gradle's wrapper. On 20 July 2017 at 14:38, Mikael Ståldal wrote: > You could install SBT on your Windows machine, and build/run the project > wit

[GitHub] logging-log4j2 pull request #94: remove unnecessary/empty comment

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/94 --- 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] [Commented] (LOG4J2-1979) Refactoring of StrSubstitutor

[ https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095296#comment-16095296 ] Gary Gregory commented on LOG4J2-1979: -- StrSubstitutor work should be done first in

Jenkins random failure

Hi All: This seems to happen randomly: Regression org.apache.logging.log4j.core.appender.rolling.RollingAppenderDirectWriteWithReconfigureTest.testRollingFileAppenderWithReconfigure Failing for the past 1 build (Since [image: Unstable]#2922

[Log4j] includeNullDelimiter

Now JsonLayout, XmlLayout, YamlLayout and GelfLayout has an includeNullDelimiter option to terminate each log event with a 0-byte. Would it be useful to have the same in any other layout? I could think of HtmlLayout, SyslogLayout and RFC5424Layout.

Jenkins build became unstable: Log4j 2.x #2922

See

[Log4j] log4j-server

The SocketServer stuff is now in the new log4j-server module, which is in the new log4j-tools repo. Is anyone going to release this new repo in conjuntion with the 2.9 release of the main repo? If not, the SocketServer stuff will be gone. If we want to have a binary release of the SocketServe

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

You could install SBT on your Windows machine, and build/run the project without using the "sbt" script in Matt's repo. http://www.scala-sbt.org/0.13/docs/Installing-sbt-on-Windows.html On 2017-07-20 21:21, Gary Gregory wrote: Hi Matt, I'm on Windows, so that sbt script is not going to work

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

You can just download SBT from their site and it'll work: http://www.scala-sbt.org/download.html On 20 July 2017 at 14:21, Gary Gregory wrote: > Hi Matt, > > I'm on Windows, so that sbt script is not going to work for me. > > I did try it on Cygwin but no dice (unsurprisingly): > > $ ./sbt run >

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

Hi Matt, I'm on Windows, so that sbt script is not going to work for me. I did try it on Cygwin but no dice (unsurprisingly): $ ./sbt run ./sbt: line 5: $'\r': command not found : invalid option nameipefail ./sbt: line 7: $'\r': command not found ./sbt: line 10: $'\r': command not found ./sbt: l

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

I just tried a Maven build again with the IBM JDK and it still crashes but the build ends this time: https://pastebin.com/Lgq98MjF Gary On Thu, Jul 20, 2017 at 12:14 PM, Matt Sicker wrote: > https://github.com/jvz/test-log4j-scala > > Clone this and run "sbt run" or "./sbt run". It should print

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

https://github.com/jvz/test-log4j-scala Clone this and run "sbt run" or "./sbt run". It should print out a single info-level "Hello, world!" log message. On 20 July 2017 at 14:03, Matt Sicker wrote: > I can write a test project that you can try out with the IBM JDK. I'll > push something to Git

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

I can write a test project that you can try out with the IBM JDK. I'll push something to GitHub this afternoon. On 20 July 2017 at 13:59, Gary Gregory wrote: > On Thu, Jul 20, 2017 at 11:54 AM, Mikael Ståldal wrote: > > > On 2017-07-20 03:16, Gary Gregory wrote: > > > >> I noticed WARNINGs like

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

On Thu, Jul 20, 2017 at 11:54 AM, Mikael Ståldal wrote: > On 2017-07-20 03:16, Gary Gregory wrote: > >> I noticed WARNINGs like: >> >> [INFO] --- scala-maven-plugin:3.2.2:compile (default) @ >> log4j-api-scala_2.11 --- >> [WARNING] Expected all dependencies to require Scala version: 2.11.8 >> [W

[jira] [Resolved] (LOG4J2-1982) Log4j-config.xsd only allows one AppenderRef element for each Logger element

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

[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=16095198#comment-16095198 ] Mikael Ståldal commented on LOG4J2-1921: log4j-core does not support Android, and

[jira] [Commented] (LOG4J2-1982) Log4j-config.xsd only allows one AppenderRef element for each Logger element

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

[jira] [Updated] (LOG4J2-1982) Log4j-config.xsd only allows one AppenderRef element for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1982: - Summary: Log4j-config.xsd only allows one AppenderRef element for each Logger element (was: log2

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

On 2017-07-20 03:16, Gary Gregory wrote: I noticed WARNINGs like: [INFO] --- scala-maven-plugin:3.2.2:compile (default) @ log4j-api-scala_2.11 --- [WARNING] Expected all dependencies to require Scala version: 2.11.8 [WARNING] org.apache.logging.log4j:log4j-api-scala_2.11:11.0 requires scala ve

[GitHub] logging-log4j2 issue #82: Add a new LuceneAppender which writes logging even...

Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/82 You can add docs to the [appenders page](https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/manual/appenders.xml). The basic format is HTML currently. You can just follow the patte

Re: [log4net] ci pipeline status update

Hi I've just disabled both old build jobs in jenkins before they get on our nerves. :-) Further I've updated the following files both to be in markup and parts of their contents to reflect more the current state of the project: * README * CONTRIBUTING * ReleaseInstructions Please note that Relea

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

See Changes: [dpsenner] Contributing: moved sections and improved the cd-pipeline section -- [...truncated 2.85 KB...] > git rev-parse "refs/tags/rc/1.2.13-RC3^{commit}

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

See Changes: [dpsenner] Contributing: the link struggling continues.. -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > gi

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

See Changes: [dpsenner] Contributing: yet another attempt to fix that link -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10

[GitHub] logging-log4j2 issue #82: Add a new LuceneAppender which writes logging even...

Github user liyuj commented on the issue: https://github.com/apache/logging-log4j2/pull/82 I can provide, but what does it contain? In what format? --- 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

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

See Changes: [dpsenner] Contributing: fixed last added link -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git rev-pars

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

See

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

See Changes: [dpsenner] ReleaseInstructions: fixed a few code quotes [dpsenner] Contributing: added link to the continuous deployment pipeline -- [...truncated 2.91 KB.

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

See Changes: [dpsenner] ReleaseInstructions: fixed a few code quotes -- [...truncated 1.57 KB...] Seen branch in repository origin/master Seen branch in repository origi

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

See Changes: [dpsenner] ReleaseInstructions: moved important remark section to the top -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" #

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

See Changes: [dpsenner] ReleaseInstructions: visited all links and improved introduction section -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^

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

See Changes: [dpsenner] ReleaseInstructions: renamed file to hint that it is in markup format [dpsenner] ReleaseInstructions: refactored to markup format -- [...truncat

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

See Changes: [dpsenner] Contributing: fixed link to the log4net jira project -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=1

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

See

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

See Changes: [dpsenner] Contributing: fixed wording and phrasing in several places -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # tim

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

See Changes: [dpsenner] Contributing: rewrote great parts of the document to reflect the current -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^

[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=16094647#comment-16094647 ] Remko Popma commented on LOG4J2-1921: - My understanding is that log4j-api-android is

[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=16094625#comment-16094625 ] Ralph Goers commented on LOG4J2-1921: - You should not have needed Log4J-core. > Gett

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

See Changes: [dpsenner] (doc) Contributing: added a code of conduct section -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10

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

See Changes: [dpsenner] (doc) Contributing: improved the build job section -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10

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

See Changes: [dpsenner] (doc) Contributing: fixed the syntax typos on a few links -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # time

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

See Changes: [dpsenner] (doc) Contributing: fixed markup syntax of unordered lists -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # tim

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

See Changes: [dpsenner] Readme: updated readme to markup syntax and added a reference to -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}"

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

See Changes: [dpsenner] Contributing: fixed whitespaces and typos -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git re

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

See Changes: [dpsenner] Contributing: reformatted to markup syntax -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git r

[jira] [Created] (LOG4J2-1982) log24-config.xsd only allows one AppenderRef element for each Logger element

Christoph Lembeck created LOG4J2-1982: - Summary: log24-config.xsd only allows one AppenderRef element for each Logger element Key: LOG4J2-1982 URL: https://issues.apache.org/jira/browse/LOG4J2-1982

[jira] [Commented] (LOG4J2-1979) Refactoring of StrSubstitutor

[ https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094491#comment-16094491 ] João Paulo Lemes Machado commented on LOG4J2-1979: -- Hi Matt, I sent the

[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=16094482#comment-16094482 ] Ajitha commented on LOG4J2-1921: Hi Team, I did as mentioned above. I built logging-log4