Re: Java 9, 8, 7 and Eclipse

On Thu, May 4, 2017 at 10:32 PM, Gary Gregory wrote: > Ah, I had Java 9. I set JAVA_HOME to Java 8 and it's off and running (in > the core tests now...) > OMG, my first build passed under this new regime. Phew! ;-) G > > Thank you! > Gary > > On Thu, May 4, 2017 at 10:01 PM, Ralph Goers > wro

Re: Java 9, 8, 7 and Eclipse

Ah, I had Java 9. I set JAVA_HOME to Java 8 and it's off and running (in the core tests now...) Thank you! Gary On Thu, May 4, 2017 at 10:01 PM, Ralph Goers wrote: > What do you get when you run java -version? It has to be Java 7 or 8. > > Ralph > > > On May 4, 2017, at 9:16 PM, Gary Gregory w

Re: Java 9, 8, 7 and Eclipse

What do you get when you run java -version? It has to be Java 7 or 8. Ralph > On May 4, 2017, at 9:16 PM, Gary Gregory wrote: > > I installed a toolchain.xml (the one I committed the root) and ran 'mvn > clean install' and I still get: > > [ERROR] Failed to execute goal > org.apache.maven.plug

Re: Java 9, 8, 7 and Eclipse

I installed a toolchain.xml (the one I committed the root) and ran 'mvn clean install' and I still get: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project log4j-core: Execution default-test of goal org.apache.maven.plugins:maven-sure

Re: Java 9, 8, 7 and Eclipse

For a clearer explanation - If you look at the parent pom you will notice that there are two executions within the compiler plugin. The first is the default compile that excludes module-info.java, I have no idea why they decided to have this file have a .java extension since the file name seems

Re: Java 9, 8, 7 and Eclipse

This is documented in src/site/markdown/build.md and in BUILDING.md. If you feel the wording can be improved feel free to update it. Ralph > On May 4, 2017, at 8:32 PM, Ralph Goers wrote: > > I run “mvn clean install” from the command line. I have Java 7, 8 and 9 > installed on my computers.

Re: Java 9, 8, 7 and Eclipse

I run “mvn clean install” from the command line. I have Java 7, 8 and 9 installed on my computers. Java 8 happens to be the default on my work computer and Java 7 is the default on the computer where I release Log4j from. I have toolchains configured in ~/.m2/toolchains.xml with jd

Re: Java 9, 8, 7 and Eclipse

On Thu, May 4, 2017 at 7:45 PM, Ralph Goers wrote: > I get the same thing on my Mac when building only with Java 9. I normally > build with Java 8 or 7 as the default JDK and use toolchains for the Java 9 > specific stuff, so all the tests are run in Java 7 or 8 - except when I > specifically wan

Re: Java 9, 8, 7 and Eclipse

This has been reported as https://issues.apache.org/jira/browse/SUREFIRE-1265 . The good news is that it is fixed. The bad news is that version 2.20.1 has not been released yet. Ralph > On May 4, 2017, at 7:45 PM, Ralph Goers wrote: > > I g

Re: Java 9, 8, 7 and Eclipse

I get the same thing on my Mac when building only with Java 9. I normally build with Java 8 or 7 as the default JDK and use toolchains for the Java 9 specific stuff, so all the tests are run in Java 7 or 8 - except when I specifically wanted to test the StackWalker support. I tested that through

[jira] [Created] (LOG4J2-1893) JdkMapAdapterStringMap#toMap can return an immutable map

Kenny MacLeod created LOG4J2-1893: - Summary: JdkMapAdapterStringMap#toMap can return an immutable map Key: LOG4J2-1893 URL: https://issues.apache.org/jira/browse/LOG4J2-1893 Project: Log4j 2

Re: Type of org.apache.logging.log4j.core.net.ssl.StoreConfiguration.password

Unsubscribe On May 4, 2017 8:06 PM, "Gary Gregory" wrote: > Hi, > > I think I'd like to change the type > of org.apache.logging.log4j.core.net.ssl.StoreConfiguration.password from > String to char[] for the usual security reason. > > Thoughts? > > Gary > > -- > E-Mail: garydgreg...@gmail.com | g

Re: Java 9, 8, 7 and Eclipse

When I build with Java 9 EA 167 and Maven I get: [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Log4j 2 . SUCCESS [ 2.492 s] [INFO] Apache Log4j API ..

Re: [Log4j] log4j-server

On Thu, May 4, 2017 at 5:16 PM, Remko Popma wrote: > Why don't we focus on making the build faster instead of this module & > repo break-up? > > We know this breakup is adding all kinds of complexity but we are only > *hoping* (not sure) that it will make the build faster. > > The way I've heard

RAT check failures

Hi All: I'd fix this but my dev env (Eclipse) is completely broken ATM. Files with unapproved licenses: C:/vcs/git/apache/logging/logging-log4j2/log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/convert/Base64Converter.java C:/vcs/git/apache/logging/logging-log4j2/log4j-cor

Re: [Log4j] log4j-server

Why don't we focus on making the build faster instead of this module & repo break-up? We know this breakup is adding all kinds of complexity but we are only *hoping* (not sure) that it will make the build faster. The way I've heard Ralph and Matt describe it, the build currently requires the

Type of org.apache.logging.log4j.core.net.ssl.StoreConfiguration.password

Hi, I think I'd like to change the type of org.apache.logging.log4j.core.net.ssl.StoreConfiguration.password from String to char[] for the usual security reason. Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: Java 9, 8, 7 and Eclipse

If you figure out how to set it up in Eclipse, please share your instructions. I'm guessing you're not the only Eclipse user here. On 4 May 2017 at 18:17, Gary Gregory wrote: > On Thu, May 4, 2017 at 4:06 PM, Gary Gregory > wrote: > > > Hi all, > > > > I am trying to compile our Java trunk in E

Re: Java 9, 8, 7 and Eclipse

On Thu, May 4, 2017 at 4:06 PM, Gary Gregory wrote: > Hi all, > > I am trying to compile our Java trunk in Eclipse with Eclipse 4.7M6 and > the Java 9 BETA support. I get a compile error in > org.apache.logging.log4j.util.StackWalkerStackLocator because > StackLocator is not found. Where does tha

Re: Java 9, 8, 7 and Eclipse

Hi all, I am trying to compile our Java trunk in Eclipse with Eclipse 4.7M6 and the Java 9 BETA support. I get a compile error in org.apache.logging.log4j.util.StackWalkerStackLocator because StackLocator is not found. Where does that interface live? G On Thu, May 4, 2017 at 2:58 PM, Gary Gregor

Java 9, 8, 7 and Eclipse

Does anyone have trunk set up in Eclipse? I'm having a hell of a time getting the current trunk to build in Eclipse... Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [Log4j] log4j-server

The log4j-core repo requires Java 9 to build, so I don't see that Java 8 limitation as a problem in retrospect. On 4 May 2017 at 12:12, Ralph Goers wrote: > What refactoring? Most of the stuff that would move doesn’t change much. > > Ralph > > > On May 4, 2017, at 10:11 AM, Gary Gregory > wrot

Re: [Log4j] log4j-server

What refactoring? Most of the stuff that would move doesn’t change much. Ralph > On May 4, 2017, at 10:11 AM, Gary Gregory wrote: > > But if the server stuff (or anything else) is in a separate repo, it makes > refactoring more of a pain. > > Gary > > On Thu, May 4, 2017 at 9:58 AM, Ralph Go

Re: [Log4j] log4j-server

But if the server stuff (or anything else) is in a separate repo, it makes refactoring more of a pain. Gary On Thu, May 4, 2017 at 9:58 AM, Ralph Goers wrote: > Because the build takes forever. > > Ralph > > > On May 4, 2017, at 9:00 AM, Mikael Ståldal > wrote: > > > > I am not sure it is wort

[jira] [Comment Edited] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996769#comment-15996769 ] Oleksandr Potomkin edited comment on LOG4J2-1182 at 5/4/17 5:03 PM: ---

Re: [Log4j] log4j-server

Because the build takes forever. Ralph > On May 4, 2017, at 9:00 AM, Mikael Ståldal wrote: > > I am not sure it is worth the effort to keep things in different repos at > this point. > > I can see a point in keeping the Scala stuff in its own repo since it needs > Java 8 and scala compiler for

Re: [Log4j] log4j-server

I am not sure it is worth the effort to keep things in different repos at this point. I can see a point in keeping the Scala stuff in its own repo since it needs Java 8 and scala compiler for building. The same goes for log4j-kotlin and any other language bindings we might want to do. But for log

Re: [Log4j] log4j-server

On Thu, May 4, 2017 at 8:08 AM, Matt Sicker wrote: > I think we should really get the other git repos released before we make a > 2.9 release. The thing holding that back, in my opinion, is figuring out > how to manage the website and documentation for all these separate modules > that aren't eve

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

Done. On Thu, May 4, 2017 at 5:16 PM, Matt Sicker wrote: > As long as the plugin configuration that's exposed doesn't leak any > internal details specific to HttpURLConnection, I think we'll be fine as > you say. I haven't looked closely at the code yet, though (working hours > for me right now)

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

As long as the plugin configuration that's exposed doesn't leak any internal details specific to HttpURLConnection, I think we'll be fine as you say. I haven't looked closely at the code yet, though (working hours for me right now), so I don't have specific suggestions yet. On 4 May 2017 at 10:15,

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

I would say that the HttpManager would be that facade. If you want another implementation you write another HttpManager and add support for selecting between different managers in HttpAppender. I don't think that much code in HttpManager can be shared between different implementations. Maybe we sh

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

Depends on the use case. Using HttpURLConnection covers a lot of them, but users may need more customization to handle their requests. I'm not so sure how necessary it is to support in an initial version, but abstracting the use of HttpURLConnection behind a facade would be handy for future extensi

Re: [Log4j] log4j-server

I think we should really get the other git repos released before we make a 2.9 release. The thing holding that back, in my opinion, is figuring out how to manage the website and documentation for all these separate modules that aren't even in the same Maven project anymore. On 4 May 2017 at 09:44,

Re: [Log4j] Plans for modularization

I was thinking a little bit about the idea behind the SPI module. One aspect I was hoping for, though it may be unnecessary, was having a nice clean way to separate the implementation of the implementation so to say. The way I see it, there are a few major components of a logging system: * Logging

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

Yes, but what benefits would the more advanced client bring us? On Thu, May 4, 2017 at 4:59 PM, Matt Sicker wrote: > The main thing I wanted regarding plugability of clients was to allow for > both java.net usage along with a more advanced client. It could be > simplified down to only allowing o

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

The main thing I wanted regarding plugability of clients was to allow for both java.net usage along with a more advanced client. It could be simplified down to only allowing one non-java.net client library. I don't want to have two HTTP plugins with different configurations and other confusion jus

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

I can see advantages in using Netty-http or similar to use async NIO, though those advantages will be a bit limited as long as we don't have a proper interface for async appenders (LOG4J2-1797 ). But are there any significant advantages in using a

[Log4j] log4j-server

I have extracted the SocketServer stuff from log4j-core to new log4j-server module: https://issues.apache.org/jira/browse/LOG4J2-1851 That module is in the new logging-log4j-tools repo. However, that repo is not ready for making a release. Is anyone going to do that before the 2.9 release, or shou

Re: [1/2] logging-log4j2 git commit: LOG4J2-1442 Generic HTTP appender

Thanks for starting this! My idea in mind when I wrote the ticket was to make the actual client pluggable so that users could use HttpURLConnection (no dependencies), Apache HttpClient, Netty-HTTP, etc. On 4 May 2017 at 07:49, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/head

[jira] [Commented] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996786#comment-15996786 ] Matt Sicker commented on LOG4J2-1892: - https://github.com/conversant/disruptor/blob/m

Re: [Log4j] Deprecate SerializedLayout and remove it as default

For receiving log messages, though that's a separate feature. On 4 May 2017 at 02:57, Mikael Ståldal wrote: > We are talking about layouts now, why would we need JSON deserialization? > > On Wed, May 3, 2017 at 9:49 PM, Matt Sicker wrote: > > > I'll make a ticket for adding dependency-free JSON

[GitHub] logging-log4j2 issue #71: [LOG4J2-1874] Add ByteBufferDestionation.write(Byt...

Github user remkop commented on the issue: https://github.com/apache/logging-log4j2/pull/71 Apologies for the delay. I now have some time to start looking at this again. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[jira] [Commented] (LOG4J2-1874) Add ByteBufferDestionation.write(ByteBuffer) and write(byte[], int, int) methods and call them from TextEncoderHelper whenever possible

[ https://issues.apache.org/jira/browse/LOG4J2-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996772#comment-15996772 ] ASF GitHub Bot commented on LOG4J2-1874: Github user remkop commented on the issu

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996769#comment-15996769 ] Oleksandr Potomkin commented on LOG4J2-1182: I had the same problem issue rec

Re: [Log4j] Appender error handling

But in this case the appender is created without problems and both errors occurs later when logging an event. (I configured FileAppender with createOnDemand="true" to acheive this effect.) On Thu, May 4, 2017 at 3:40 PM, Ralph Goers wrote: > There is a difference between errors that occur when

Re: [Log4j] Appender error handling

There is a difference between errors that occur when creating the Appender vs errors that occur in logging events. If an error occurs creating the Appender the rest of the configuration should be processed so that at least some logging works. If the error is too bad then the configuration will f

[jira] [Comment Edited] (LOG4J2-1442) Add generic HTTP verb appender

[ https://issues.apache.org/jira/browse/LOG4J2-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996717#comment-15996717 ] Mikael Ståldal edited comment on LOG4J2-1442 at 5/4/17 1:30 PM: ---

[jira] [Commented] (LOG4J2-1442) Add generic HTTP verb appender

[ https://issues.apache.org/jira/browse/LOG4J2-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996717#comment-15996717 ] Mikael Ståldal commented on LOG4J2-1442: I have this almost finished now, have a

[Log4j] Appender error handling

AbstractOutputStreamAppender have this code: public void append(final LogEvent event) { try { tryAppend(event); } catch (final AppenderLoggingException ex) { error("Unable to write to stream " + manager.getName() + " for appender " + getName() + ": " + ex); throw ex

Re: The Apache Software Foundation Welcomes 64 New Members

Thanks Stefan! I'm glad to have become part of the family and look forward to a journey that is going to last for long. On 2017-05-04 11:48, Stefan Bodewig wrote: On 2017-05-04, Mikael Ståldal wrote: Congratulations Matt! Yes, congrats to Matt and Dominik. Stefan

[jira] [Commented] (LOG4J2-1442) Add generic HTTP verb appender

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

[jira] [Commented] (LOG4J2-1442) Add generic HTTP verb appender

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

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Environment: OSX 10.11 JDK 7 Jetty 9.2 but also observed in Docker container JDK 8/Tomcat 8 was:JDK 7

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Environment: JDK 7/Jetty 9.2 but also observed in JDK 8/Tomcat 8 (was: JDK 7, Jetty 9.2 but also observe

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Attachment: with spinPolicy BLOCKING.png > High constant CPU usage with Async appender DisruptorBlockingQ

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Attachment: with spinPolicy WAITING.png > High constant CPU usage with Async appender DisruptorBlockingQu

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Description: With {{spinPolicy="WAITING"}} CPU usage shoots up to 11% and stays right there with no app

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Description: With {{spinPolicy="WAITING"}} CPU usage shoots up to 11% and stays right there with no app

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Description: With {{spinPolicy="WAITING"}} CPU usage shoots up to 11% and stays right there with no app

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Description: With {{spinPolicy="WAITING"}} CPU usage shoots up to 11% and stays right there with no app

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Description: With {{spinPolicy="WAITING"}} CPU usage shoots up to 11% and stays right there with no app

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Description: With {{spinPolicy="WAITING"}} CPU usage shoots up to 11% and stays right there with no app

[jira] [Updated] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING'

[ https://issues.apache.org/jira/browse/LOG4J2-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel R updated LOG4J2-1892: - Summary: High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING' (was: H

[jira] [Created] (LOG4J2-1892) High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING`

Daniel R created LOG4J2-1892: Summary: High constant CPU usage with Async appender DisruptorBlockingQueue spinPolicy 'WAITING` Key: LOG4J2-1892 URL: https://issues.apache.org/jira/browse/LOG4J2-1892 Proje

Re: The Apache Software Foundation Welcomes 64 New Members

On 2017-05-04, Mikael Ståldal wrote: > Congratulations Matt! Yes, congrats to Matt and Dominik. Stefan

Re: [Log4j] Appender configuration error

Do we have any good example in the code to follow? On Thu, May 4, 2017 at 2:47 AM, Remko Popma wrote: > Yes, if you search for "ignoring" you should find a few other places where > error handling is done similarly. > > (Shameless plug) Every java main() method deserves http://picocli.info > > >

Re: The Apache Software Foundation Welcomes 64 New Members

Congratulations Matt! On Wed, May 3, 2017 at 10:36 PM, Gary Gregory wrote: > Congrats Matt on your Apache Membership! > > Gary > > > > From: Sally Khudairi > Sent: Wednesday, May 3, 2017 11:41:34 AM > To: Apache Announce List > Subject: The Apache Software Found

Re: [Log4j] Deprecate SerializedLayout and remove it as default

We are talking about layouts now, why would we need JSON deserialization? On Wed, May 3, 2017 at 9:49 PM, Matt Sicker wrote: > I'll make a ticket for adding dependency-free JSON serialization and > deserialization (probably separate tickets). > > On 3 May 2017 at 12:57, Remko Popma wrote: > > >

Re: [Log4j] Deprecate SerializedLayout and remove it as default

FWIW, if we want to do dependency- and garbage-free JSON serialization (not parsing), we have org.apache.logging.log4j.core.util.JsonUtils in log4j-core (used by GelfLayout). On Wed, May 3, 2017 at 10:43 PM, Matt Sicker wrote: > Remko has a ticket with a proposed binary logging format. Does tha