Re: Performance page for next release.

I was thinking along similar lines about keeping the old results and adding a set of results for the later versions. On the other hand I want to avoid information overload. Let me think about how to present it. Sent from my iPhone > On Mar 4, 2017, at 3:24, Gary Gregory wrote: > > I think we

Re: Performance page for next release.

I think we should keep the current doc pages on the site perhaps under a different heading. This would be interesting for people who cannot keep up with the latest. Gary On Fri, Mar 3, 2017 at 1:20 PM, Remko Popma wrote: > Yes but only the JMH benchmarks. Is that acceptable? > > The latency tes

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #30

See Changes: [rgoers] Add recent article [rgoers] LOG4J2-1836 - Update the API version [rgoers] LOG4J2-1836 - Update the API v

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #30

See Changes: [rgoers] Add recent article [rgoers] LOG4J2-1836 - Update the API version [rgoers] LOG4J2-1836 - Update the API v

Re: Performance page for next release.

Ok. I'll focus on those. Sent from my iPhone > On Mar 3, 2017, at 22:49, Ralph Goers wrote: > > I am most concerned with the two things that have been most impacted - the > FileAppenderBenchmark and the MarkerFilterBenchmark. > > Ralph > >> On Mar 3, 2017, at 2:20 PM, Remko Popma wrote: >>

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895092#comment-15895092 ] Remko Popma commented on LOG4J2-1259: - Do you want to provide a patch for the Log4j2

Re: Performance page for next release.

I am most concerned with the two things that have been most impacted - the FileAppenderBenchmark and the MarkerFilterBenchmark. Ralph > On Mar 3, 2017, at 2:20 PM, Remko Popma wrote: > > Yes but only the JMH benchmarks. Is that acceptable? > > The latency tests and the non-JMH Async Logger te

Re: Performance page for next release.

Yes but only the JMH benchmarks. Is that acceptable? The latency tests and the non-JMH Async Logger tests are too involved... One thing to bear in mind, we carefully documented the versions of the libraries we compared against with our benchmark results. The fact that newer versions of these l

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895026#comment-15895026 ] Veit Guna commented on LOG4J2-1259: --- Ok, I figured it out. If spring context listener i

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894991#comment-15894991 ] Veit Guna commented on LOG4J2-1259: --- Funny thing is: when adding the 2.5 stuff to web.x

[jira] [Comment Edited] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894974#comment-15894974 ] Veit Guna edited comment on LOG4J2-1259 at 3/3/17 8:33 PM: --- I j

[jira] [Comment Edited] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894974#comment-15894974 ] Veit Guna edited comment on LOG4J2-1259 at 3/3/17 8:24 PM: --- I j

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894974#comment-15894974 ] Veit Guna commented on LOG4J2-1259: --- I just ran into the same problem using 2.8.1. I'v

Re: Log4j-provider.properties API version

I've been wondering about this myself. I think we should re-look at how providers are specified as the current solution didn't work well with OSGi. Plus we kept forgetting to update it with new API versions. On 3 March 2017 at 13:17, Ralph Goers wrote: > I created LOG4J2-1836 to address this. >

[jira] [Commented] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894963#comment-15894963 ] Matt Sicker commented on LOG4J2-1835: - Oh I had totally forgotten that MPL is weak co

[jira] [Closed] (LOG4J2-1836) API Version is incorrect

[ https://issues.apache.org/jira/browse/LOG4J2-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1836. --- > API Version is incorrect > > > Key: LOG4J2-1836 >

[jira] [Commented] (LOG4J2-1836) API Version is incorrect

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

[jira] [Resolved] (LOG4J2-1836) API Version is incorrect

[ https://issues.apache.org/jira/browse/LOG4J2-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1836. - Resolution: Fixed Fix Version/s: 2.8.2 > API Version is incorrect > --

[jira] [Commented] (LOG4J2-1836) API Version is incorrect

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

[jira] [Commented] (LOG4J2-969) Refactor SyslogAppender so that Layout is a Plugin element

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

[jira] [Resolved] (LOG4J2-1810) Upgrade Logback to version 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1810. - Resolution: Fixed Fix Version/s: (was: 2.8.2) 2.8.1 > Upgrade Logba

Re: Log4j-provider.properties API version

I created LOG4J2-1836 to address this. Ralph > On Mar 3, 2017, at 12:01 PM, Ralph Goers wrote: > > Likewise, I suspect that ProviderUtil should only list 2.6.0 as a compatible > version since the implementation must be at that level or higher. > > Ralph > >> On Mar 3, 2017, at 11:58 AM, Ralp

[jira] [Created] (LOG4J2-1836) API Version is incorrect

Ralph Goers created LOG4J2-1836: --- Summary: API Version is incorrect Key: LOG4J2-1836 URL: https://issues.apache.org/jira/browse/LOG4J2-1836 Project: Log4j 2 Issue Type: Bug Components

[jira] [Updated] (LOG4J2-1381) Documentation for LoggerNameLevelRewritePolicy is wrong

[ https://issues.apache.org/jira/browse/LOG4J2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1381: Fix Version/s: (was: 2.8.1) 2.8.2 > Documentation for LoggerNameLevelRewrite

[jira] [Updated] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1229: Fix Version/s: (was: 2.8.1) 2.8.2 > Error creating logger >

[jira] [Updated] (LOG4J2-1498) [Java 9] fix dependency on old JDK versioning scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1498: Fix Version/s: (was: 2.8.1) 2.8.2 > [Java 9] fix dependency on old JDK versi

[jira] [Updated] (LOG4J2-915) Wrong timestamp of filename when SizeBasedTriggering and TimeBasedTrigger used simultaniously with RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-915: --- Fix Version/s: (was: 2.8.1) 2.8.2 > Wrong timestamp of filename when SizeBasedT

[jira] [Updated] (LOG4J2-1341) (GC) Avoid allocating temporary objects in Pattern Converters for PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1341: Fix Version/s: (was: 2.8.1) 2.8.2 > (GC) Avoid allocating temporary objects

[jira] [Updated] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1812: Fix Version/s: (was: 2.8.1) 2.8.2 > Improve error message when log4j 2 confi

[jira] [Updated] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1086: Fix Version/s: (was: 2.8.1) 2.8.2 > SizeBasedTriggeringPolicy is not working

[jira] [Updated] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1576: Fix Version/s: (was: 2.8.1) 2.8.2 > Better automated backwards compatibility

[jira] [Updated] (LOG4J2-1603) Redo hashCode() and equals() methods in org.apache.logging.log4j.core.net.ssl classes.

[ https://issues.apache.org/jira/browse/LOG4J2-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1603: Fix Version/s: (was: 2.8.1) 2.8.2 > Redo hashCode() and equals() methods in

[jira] [Updated] (LOG4J2-1521) StringIndexOutOfBoundsException thrown when rolling logs

[ https://issues.apache.org/jira/browse/LOG4J2-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1521: Fix Version/s: (was: 2.8.1) 2.8.2 > StringIndexOutOfBoundsException thrown w

[jira] [Updated] (LOG4J2-1760) AsyncAppender with LinkedTransferQueue.offer()

[ https://issues.apache.org/jira/browse/LOG4J2-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1760: Fix Version/s: (was: 2.8.1) 2.8.2 > AsyncAppender with LinkedTransferQueue.o

[jira] [Updated] (LOG4J2-1013) Log4j2 Main Arguments Lookup by name doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1013: Fix Version/s: (was: 2.8.1) 2.8.2 > Log4j2 Main Arguments Lookup by name doe

[jira] [Updated] (LOG4J2-1810) Upgrade Logback to version 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1810: Fix Version/s: (was: 2.8.1) 2.8.2 > Upgrade Logback to version 1.2 > ---

[jira] [Updated] (LOG4J2-1130) CsvLogEventLayout NanoTime timestamp is always zero.

[ https://issues.apache.org/jira/browse/LOG4J2-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1130: Fix Version/s: (was: 2.8.1) 2.8.2 > CsvLogEventLayout NanoTime timestamp is

[jira] [Updated] (LOG4J2-1593) Concrete Filter implementations should override equals and hashCode

[ https://issues.apache.org/jira/browse/LOG4J2-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1593: Fix Version/s: (was: 2.8.1) 2.8.2 > Concrete Filter implementations should o

[jira] [Updated] (LOG4J2-1246) PatternLayout %date conversion pattern should render time zone designator for ISO-ISO8601

[ https://issues.apache.org/jira/browse/LOG4J2-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1246: Fix Version/s: (was: 2.8.1) 2.8.2 > PatternLayout %date conversion pattern s

[jira] [Updated] (LOG4J2-1261) Replace usage of deprecated LMAX Disruptor APIs

[ https://issues.apache.org/jira/browse/LOG4J2-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1261: Fix Version/s: (was: 2.8.1) 2.8.2 > Replace usage of deprecated LMAX Disrupt

[jira] [Updated] (LOG4J2-1395) Add "direct" option to ConsoleAppender for increased performance

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1395: Fix Version/s: (was: 2.8.1) 2.8.2 > Add "direct" option to ConsoleAppender f

[jira] [Updated] (LOG4J2-1410) Add new LiteTimeoutBlockingWaitStrategy for Async Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1410: Fix Version/s: (was: 2.8.1) 2.8.2 > Add new LiteTimeoutBlockingWaitStrategy

[jira] [Updated] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1477: Fix Version/s: (was: 2.8.1) 2.8.2 > @NonNull support (for @NonNullByDefault

[jira] [Updated] (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 ] Ralph Goers updated LOG4J2-1813: Fix Version/s: (was: 2.8.1) 2.8.2 > Provide shorter and more intuitive way t

[jira] [Updated] (LOG4J2-1594) Add support for adding and removing Filters via JMX

[ https://issues.apache.org/jira/browse/LOG4J2-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1594: Fix Version/s: (was: 2.8.1) 2.8.2 > Add support for adding and removing Filt

[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy

[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1198: Fix Version/s: (was: 2.8.1) 2.8.2 > Add support for custom rollover strategy

[jira] [Updated] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1705: Fix Version/s: (was: 2.8.1) 2.8.2 > Kotlin wrapper for Log4j 2 API > ---

[jira] [Updated] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1699: Fix Version/s: (was: 2.8.1) 2.8.2 > Configurable Log File Permissions with P

[jira] [Updated] (LOG4J2-1534) Create alias 'statusDestination' for 'dest' attribute in Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1534: Fix Version/s: (was: 2.8.1) 2.8.2 > Create alias 'statusDestination' for 'de

[jira] [Updated] (LOG4J2-1116) Web app-friendly thread locals for gc-free logging (was: upgrade to log4j2 causes too frequent minor gc)

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1116: Fix Version/s: (was: 2.8.1) 2.8.2 > Web app-friendly thread locals for gc-fr

Re: Log4j-provider.properties API version

Likewise, I suspect that ProviderUtil should only list 2.6.0 as a compatible version since the implementation must be at that level or higher. Ralph > On Mar 3, 2017, at 11:58 AM, Ralph Goers wrote: > > The Log4jAPIVersion in log4j-provider.properties in log4j-core says it > supports the 2.1.

Log4j-provider.properties API version

The Log4jAPIVersion in log4j-provider.properties in log4j-core says it supports the 2.1.0 API. Is that actually correct? I suspect that if you try to use the log4j 2.1 API jar with the log4j 2.8.1 core jar there will be problems. Doesn’t Log4j core require a Log4j API jar that is at least at t

[jira] [Commented] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894811#comment-15894811 ] Konstantin Gribov commented on LOG4J2-1835: --- Because of [zeromq project recomen

[jira] [Commented] (LOG4J2-1824) (GC) Avoid allocating temporary objects in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894693#comment-15894693 ] Matt Sicker commented on LOG4J2-1824: - An unrolled Producer method would certainly al

[jira] [Commented] (LOG4J2-1824) (GC) Avoid allocating temporary objects in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894681#comment-15894681 ] Mikael Ståldal commented on LOG4J2-1824: Yes. I would prefer if Kafka client cou

[jira] [Commented] (LOG4J2-1824) (GC) Avoid allocating temporary objects in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894656#comment-15894656 ] Matt Sicker commented on LOG4J2-1824: - Then it seems the only way to implement this w

Re: Roadmap for 2.8.1

The Scala language versions is already done the same standard way everyone implements Scala libraries (hence the strange naming scheme we already have). I'd imagine that the versions can be completely decoupled by specifying a minimum Log4j API version it requires (though should generally be whatev

Performance page for next release.

Remko, Would it be possible for you to update the performance page for the next release? I am uncomfortable with some of the results because I know they have changed since 2.6. Ralph - To unsubscribe, e-mail: log4j-dev-unsu

[jira] [Commented] (LOG4J2-1824) (GC) Avoid allocating temporary objects in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894654#comment-15894654 ] Mikael Ståldal commented on LOG4J2-1824: No, Kafka ProducerRecord is immutable.

Re: [ANNOUNCEMENT] Apache Log4j 2.8.1 released

Actually, when I received my own message the HTML styling was gone. But Remko’s reply had it. Strange. Ralph > On Mar 3, 2017, at 8:44 AM, Matt Sicker wrote: > > I'm digging the new announcement format! I saw the font and immediately > though "Isn't that what they use at GitHub?" :P > > On 3

[jira] [Commented] (LOG4J2-1824) (GC) Avoid allocating temporary objects in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894651#comment-15894651 ] Matt Sicker commented on LOG4J2-1824: - We can reuse ProducerRecord objects I bet. Sin

[jira] [Commented] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894630#comment-15894630 ] Matt Sicker commented on LOG4J2-1835: - Yes, that log4j-core link is generated by Mave

Re: [ANNOUNCEMENT] Apache Log4j 2.8.1 released

I'm digging the new announcement format! I saw the font and immediately though "Isn't that what they use at GitHub?" :P On 3 March 2017 at 01:58, Remko Popma wrote: > Blogged: https://blogs.apache.org/logging/entry/log4j-2-8-1-released > > > On Fri, Mar 3, 2017 at 2:27 PM, Ralph Goers > wrote:

[jira] [Commented] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894556#comment-15894556 ] Konstantin Gribov commented on LOG4J2-1835: --- http://logging.apache.org/log4j/2.

[jira] [Created] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

Konstantin Gribov created LOG4J2-1835: - Summary: Incorrect license info for jeromq at runtime dependencies page Key: LOG4J2-1835 URL: https://issues.apache.org/jira/browse/LOG4J2-1835 Project: Log

[jira] [Commented] (LOG4J2-1824) (GC) Avoid allocating temporary objects in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894251#comment-15894251 ] Mikael Ståldal commented on LOG4J2-1824: There is another problem with the Kafka

Re: Roadmap for 2.8.1

I guess the idea is that releases of Log4j 2 and log4j-scala should be independent in both ways, right? I think I have coordination between log4j-scala and Scala language covered already. On Fri, Mar 3, 2017 at 10:19 AM, Remko Popma wrote: > Mikael, you probably need to plan your versioning sch

JDK 9 EA Build 159 and JDK 8u152 is available on java.net

Hi Nick, *JDK 8u152 **Early Access b01 *is available on java.net *JDK 9 Early Access* b159 is available on java.net, summary of changes are listed here . Th

[jira] [Commented] (LOG4J2-1825) Log4j2 throwing an error in Windows bash console

[ https://issues.apache.org/jira/browse/LOG4J2-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894188#comment-15894188 ] Ales Krestan commented on LOG4J2-1825: -- Amendment of the previous comment: I had log

[jira] [Commented] (LOG4J2-1825) Log4j2 throwing an error in Windows bash console

[ https://issues.apache.org/jira/browse/LOG4J2-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894036#comment-15894036 ] Ales Krestan commented on LOG4J2-1825: -- Unfortunately, the same issue is still prese

[jira] [Commented] (LOG4J2-1753) java.lang.ClassNotFoundException: org.apache.logging.log4j.core.util.ExecutorServices when running the OSGi tests

[ https://issues.apache.org/jira/browse/LOG4J2-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894030#comment-15894030 ] Rob Gansevles commented on LOG4J2-1753: --- This issue is still has status OPEN, but i

[jira] [Commented] (LOG4J2-1834) Handle when LogEvent.getLoggerName() returns null properly

[ https://issues.apache.org/jira/browse/LOG4J2-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894007#comment-15894007 ] Gary Gregory commented on LOG4J2-1834: -- Not sure, the Javadoc for the method says {{

[jira] [Commented] (LOG4J2-1834) Handle when LogEvent.getLoggerName() returns null properly

[ https://issues.apache.org/jira/browse/LOG4J2-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893990#comment-15893990 ] Mikael Ståldal commented on LOG4J2-1834: [~garydgregory] How to you produce a cas

[jira] [Commented] (LOG4J2-1831) NullPointerException in HtmlLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893985#comment-15893985 ] Mikael Ståldal commented on LOG4J2-1831: Other places here: https://issues.apache

[jira] [Created] (LOG4J2-1834) Handle when LogEvent.getLoggerName() returns null properly

Mikael Ståldal created LOG4J2-1834: -- Summary: Handle when LogEvent.getLoggerName() returns null properly Key: LOG4J2-1834 URL: https://issues.apache.org/jira/browse/LOG4J2-1834 Project: Log4j 2

Re: Roadmap for 2.8.1

Mikael, you probably need to plan your versioning scheme to handle any combination of the following: * log4j 2 releases: do you want to do a release for the log4j-scala modules every time? E.g., when we go from 2.8.1 to 2.8.2? My understanding is that once they are decoupled, the log4j-scala mod

[jira] [Commented] (LOG4J2-1798) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893929#comment-15893929 ] Danilo Härtzer commented on LOG4J2-1798: Still exists in 2.8, here is the actual

Re: Roadmap for 2.8.1

I would like to keep package and artifact names, and bump version to 11.0. On Mar 1, 2017 4:04 PM, "Matt Sicker" wrote: > If you change artifact ids, it's generally a good idea to change packages, > too. I've had issues in the past with Feign for instance because they > changed groupId/artifactI