[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=15884570#comment-15884570 ] Ralph Goers commented on LOG4J2-1798: - Can you please try this with 2.8. Some changes

Jenkins build became unstable: Log4j 2.x #2686

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1423) org.apache.logging.log4j.flume.appender.FlumeAppenderTest.testIncompleteBatch hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884567#comment-15884567 ] Ralph Goers commented on LOG4J2-1423: - Is this still happening? > org.apache.logging

[jira] [Assigned] (LOG4J2-1584) RFC5424 layout needs better delimiter specification between message and throwable

[ https://issues.apache.org/jira/browse/LOG4J2-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1584: --- Assignee: Ralph Goers > RFC5424 layout needs better delimiter specification between message

[jira] [Commented] (LOG4J2-1455) CompositeConfiguration Logger level not overridable

[ https://issues.apache.org/jira/browse/LOG4J2-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884566#comment-15884566 ] Ralph Goers commented on LOG4J2-1455: - So is this still a problem or can it be closed

[jira] [Commented] (LOG4J2-1376) RFC5424 Enterprise Number should be an OID fragment.

[ https://issues.apache.org/jira/browse/LOG4J2-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884565#comment-15884565 ] Ralph Goers commented on LOG4J2-1376: - Any update on this? > RFC5424 Enterprise Numb

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884562#comment-15884562 ] Ralph Goers commented on LOG4J2-1768: - Any update? We will have to close this issue i

[jira] [Resolved] (LOG4J2-1821) (not only) default rollover strategy is *broken*

[ https://issues.apache.org/jira/browse/LOG4J2-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1821. - Resolution: Fixed > (not only) default rollover strategy is *broken* > --

[jira] [Closed] (LOG4J2-546) Commons logging integration does not work in WildFly 8.0

[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-546. -- > Commons logging integration does not work in WildFly 8.0 > ---

[jira] [Resolved] (LOG4J2-546) Commons logging integration does not work in WildFly 8.0

[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-546. Resolution: Won't Fix I am closing this as "won't fix" because based on Matt's research and what I

[jira] [Commented] (LOG4J2-1784) Large values for max in DefaultRolloverStrategy blocks application

[ https://issues.apache.org/jira/browse/LOG4J2-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884556#comment-15884556 ] Ralph Goers commented on LOG4J2-1784: - Any update on this? > Large values for max in

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

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884555#comment-15884555 ] Ralph Goers commented on LOG4J2-1086: - Is there any update on this? > SizeBasedTrigg

[jira] [Resolved] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8

[ https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1804. - Resolution: Fixed Fix Version/s: 2.8.1 A modified version of the patch and test were appli

[jira] [Commented] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8

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

Re: Experimenting with NIO

I tried using a FileChannel for the FileAppender a week or so ago to see if passing the ByteBuffer to the FileChannel would improve performance since it doesn’t have to be synchronized. I didn’t see any improvement though and I ended up reverting it. But I might have done something wrong. Ralph

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

See Changes: [Matt Sicker] [LOG4J2-1823]: Remove deprecation on MessageSupplier lambda functions in [Matt Sicker] Remove excep

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

See Changes: [Matt Sicker] [LOG4J2-1823]: Remove deprecation on MessageSupplier lambda functions in [Matt Sicker] Remove excep

Experimenting with NIO

We already use a bit of NIO (ByteBuffer for layouts and appenders/managers, MappedByteBuffer for mmap'd files, FileLock for locking files, etc.), and I've been playing around with the NIO API lately. I have some sample code here to show some trivial use case of A

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884304#comment-15884304 ] Gary Gregory commented on LOG4J2-1807: -- Sounds reasonable. > [core] Add and impleme

[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=15884185#comment-15884185 ] Adonis Settouf commented on LOG4J2-1825: Fair enough, I can only test it at work,

[jira] [Resolved] (LOG4J2-1636) Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and sun.stderr.encoding

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1636. - Resolution: Fixed Fix Version/s: 2.8 2.8.1 Marking this fixed as it was

[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=15884173#comment-15884173 ] Matt Sicker commented on LOG4J2-1825: - This sounds likely to be the same issue as LOG

[jira] [Updated] (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:all-tabpanel ] Adonis Settouf updated LOG4J2-1825: --- Description: Good morning, using log4j2 in my project (see below the configuration) running

[jira] [Updated] (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:all-tabpanel ] Adonis Settouf updated LOG4J2-1825: --- Attachment: ms-dos-stacktrace log4j2.properties The properties file and the s

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

Adonis Settouf created LOG4J2-1825: -- Summary: Log4j2 throwing an error in Windows bash console Key: LOG4J2-1825 URL: https://issues.apache.org/jira/browse/LOG4J2-1825 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1797) Add asynchronous/non-blocking SPIs for appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884153#comment-15884153 ] Matt Sicker commented on LOG4J2-1797: - I found a potentially useful interface already

[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=15884139#comment-15884139 ] Matt Sicker commented on LOG4J2-1824: - One possible caveat: in Kafka, log messages ar