[jira] [Commented] (LOG4J2-1641) Update JeroMQ from 0.3.5 to 0.3.6

[ https://issues.apache.org/jira/browse/LOG4J2-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564125#comment-15564125 ] Gary Gregory commented on LOG4J2-1641: -- Changes: https://github.com/zeromq/jeromq/co

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

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Commented] (LOG4J2-1639) Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564000#comment-15564000 ] Gary Gregory commented on LOG4J2-1639: -- It does not define one. > Fix MemoryMappedF

[jira] [Commented] (LOG4J2-1639) Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563848#comment-15563848 ] Remko Popma commented on LOG4J2-1639: - (Away from PC) I forgot, what does MemoryMappe

Re: Jenkins build became unstable: Log4j 2.x #2408

Still getting these random failures: https://builds.apache.org/job/Log4j%202.x/2408/org.apache.logging.log4j$log4j-core/testReport/org.apache.logging.log4j.core.async/AsyncLoggerThreadContextGarbageFreeTest/testAsyncLogWritesToLog_1_/ Gary On Mon, Oct 10, 2016 at 3:25 PM, Apache Jenkins Server <

Jenkins build became unstable: Log4j 2.x #2408

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Commented] (LOG4J2-1633) Using "${log4j:configLocation}" in a PatternLayout header on Windows OS does not render properly

[ https://issues.apache.org/jira/browse/LOG4J2-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563547#comment-15563547 ] Gary Gregory commented on LOG4J2-1633: -- Hm... IMO we should also be using {{File.get

[jira] [Closed] (LOG4J2-1641) Update JeroMQ from 0.3.5 to 0.3.6

[ https://issues.apache.org/jira/browse/LOG4J2-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1641. Resolution: Fixed In Git master. > Update JeroMQ from 0.3.5 to 0.3.6 > ---

[jira] [Created] (LOG4J2-1641) Update JeroMQ from 0.3.5 to 0.3.6

Gary Gregory created LOG4J2-1641: Summary: Update JeroMQ from 0.3.5 to 0.3.6 Key: LOG4J2-1641 URL: https://issues.apache.org/jira/browse/LOG4J2-1641 Project: Log4j 2 Issue Type: Improvement

[jira] [Commented] (LOG4J2-1634) Root LoggerConfig is corrupted leading to stack overflow

[ https://issues.apache.org/jira/browse/LOG4J2-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563437#comment-15563437 ] Gary Gregory commented on LOG4J2-1634: -- [[email protected]], Thank you for

[jira] [Updated] (LOG4J2-1639) Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1639: - Description: The documentation for {{org.apache.logging.log4j.core.appender.MemoryMappedFileAppe

[jira] [Resolved] (LOG4J2-1639) Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1639. -- Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.7.1 Thank you for you

[jira] [Updated] (LOG4J2-1639) Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1639: - Affects Version/s: 2.7 > Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush

[jira] [Updated] (LOG4J2-1639) Fix MemoryMappedFileAppender.createAppender() Javadoc

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1639: - Summary: Fix MemoryMappedFileAppender.createAppender() Javadoc (was: Mistake in the documentatio

[jira] [Updated] (LOG4J2-1639) Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1639: - Summary: Fix MemoryMappedFileAppender.createAppender() Javadoc for immediateFlush (was: Fix Memo

[jira] [Commented] (LOG4J2-1639) Mistake in the documentation

[ https://issues.apache.org/jira/browse/LOG4J2-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563419#comment-15563419 ] Gary Gregory commented on LOG4J2-1639: -- The code is correct due to commit 875cec8fc5

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15563412#comment-15563412 ] Gary Gregory commented on LOG4J2-1636: -- This is pretty bad WRT performance and our G

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15563398#comment-15563398 ] Gary Gregory commented on LOG4J2-1636: -- See my previous comment: Java 9 EA build 136

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15563185#comment-15563185 ] Eldar Gabdullin commented on LOG4J2-1636: - No need to say, that relying on {{sun.

[jira] [Issue Comment Deleted] (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 ] Eldar Gabdullin updated LOG4J2-1636: Comment: was deleted (was: No need to say, that relying on {{sun.stdout.encoding}} is a ver

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15563182#comment-15563182 ] Eldar Gabdullin commented on LOG4J2-1636: - No need to say, that relying on {{sun.

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15563146#comment-15563146 ] Ralph Goers commented on LOG4J2-1636: - This requires the change I spoke of in LOG4J2-

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15563069#comment-15563069 ] Gary Gregory commented on LOG4J2-1636: -- Please check Uploading: https://repository.

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15563069#comment-15563069 ] Gary Gregory edited comment on LOG4J2-1636 at 10/10/16 6:27 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15562849#comment-15562849 ] Gary Gregory edited comment on LOG4J2-1636 at 10/10/16 5:49 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15562849#comment-15562849 ] Gary Gregory edited comment on LOG4J2-1636 at 10/10/16 5:49 PM: ---

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15562849#comment-15562849 ] Gary Gregory edited comment on LOG4J2-1636 at 10/10/16 5:48 PM: ---

[jira] [Updated] (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 ] Gary Gregory updated LOG4J2-1636: - Description: The Oracle Java 8 platform supports two system properties to configure the System c

[jira] [Updated] (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 ] Gary Gregory updated LOG4J2-1636: - Summary: Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and sun.stderr.enc

[jira] [Updated] (LOG4J2-1636) Console Appender does not pick up Oracle Java 8's

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1636: - Summary: Console Appender does not pick up Oracle Java 8's (was: Bad console output encoding on

[jira] [Updated] (LOG4J2-1636) Bad console output encoding on Windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1636: - Summary: Bad console output encoding on Windows (was: Bad console output encoding on windows) >

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562892#comment-15562892 ] Ralph Goers commented on LOG4J2-1636: - A Layout formats the output. An Appender deli

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562851#comment-15562851 ] Gary Gregory commented on LOG4J2-1636: -- A layout is NOT a sink FWIW > Bad console o

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562849#comment-15562849 ] Gary Gregory commented on LOG4J2-1636: -- As a workaround you can set the charset on y

[jira] [Comment Edited] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562719#comment-15562719 ] Gary Gregory edited comment on LOG4J2-1636 at 10/10/16 5:13 PM: ---

[jira] [Comment Edited] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562719#comment-15562719 ] Gary Gregory edited comment on LOG4J2-1636 at 10/10/16 5:13 PM: ---

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562770#comment-15562770 ] Eldar Gabdullin commented on LOG4J2-1636: - If only there was no distinction betwe

[jira] [Assigned] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reassigned LOG4J2-1636: Assignee: Gary Gregory > Bad console output encoding on windows >

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562725#comment-15562725 ] Ralph Goers commented on LOG4J2-1636: - And I am betting we will not be able to use su

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562719#comment-15562719 ] Gary Gregory commented on LOG4J2-1636: -- Java 7: {code:java} setOut0(new PrintStream

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562691#comment-15562691 ] Gary Gregory commented on LOG4J2-1636: -- It's still a print stream, not a writer. I d

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562669#comment-15562669 ] Eldar Gabdullin commented on LOG4J2-1636: - Look here - https://gist.github.com/e

[jira] [Commented] (LOG4J2-1636) Bad console output encoding on windows

[ https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562648#comment-15562648 ] Gary Gregory commented on LOG4J2-1636: -- That's not what I see in Oracle Java 8 1.8.0

[jira] [Updated] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris McGee updated LOG4J2-1640: Description: If this isn't actually a bug, then I apologize for reporting it, but I cannot figure

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562371#comment-15562371 ] Chris McGee commented on LOG4J2-1640: - Certainly. I'll even do one better and provide

[jira] [Commented] (LOG4J2-1630) Unit of Work Logging

[ https://issues.apache.org/jira/browse/LOG4J2-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562331#comment-15562331 ] Ralph Goers commented on LOG4J2-1630: - No. > Unit of Work Logging >

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562328#comment-15562328 ] Ralph Goers commented on LOG4J2-1640: - Can you change status="WARN" to status="TRACE"

[jira] [Commented] (LOG4J2-1630) Unit of Work Logging

[ https://issues.apache.org/jira/browse/LOG4J2-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562287#comment-15562287 ] Remko Popma commented on LOG4J2-1630: - Would the {{Filter}} interface need to change?

[jira] [Created] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

Chris McGee created LOG4J2-1640: --- Summary: RollingFileAppender with CronTriggeringPolicy broken? Key: LOG4J2-1640 URL: https://issues.apache.org/jira/browse/LOG4J2-1640 Project: Log4j 2 Issue T

[jira] [Created] (LOG4J2-1639) Mistake in the documentation

Sridhar Gopinath created LOG4J2-1639: Summary: Mistake in the documentation Key: LOG4J2-1639 URL: https://issues.apache.org/jira/browse/LOG4J2-1639 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562011#comment-15562011 ] Jason Tedor commented on LOG4J2-1563: - That's a workflow that a lot of people are use

[jira] [Commented] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561773#comment-15561773 ] Mikael Ståldal commented on LOG4J2-1563: Maybe we should encourage external contr

[jira] [Commented] (LOG4J2-1630) Unit of Work Logging

[ https://issues.apache.org/jira/browse/LOG4J2-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561697#comment-15561697 ] Mikael Ståldal commented on LOG4J2-1630: Sound like making the logging system par