[jira] [Commented] (LOG4J2-2591) RollingFileAppender don't append log file after restart service.

[ https://issues.apache.org/jira/browse/LOG4J2-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869802#comment-16869802 ] Ralph Goers commented on LOG4J2-2591: - Please try with the latest code in the release-2.x branch. I

[jira] [Comment Edited] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869658#comment-16869658 ] Ralph Goers edited comment on LOG4J2-2636 at 6/21/19 4:40 PM: -- The

[jira] [Commented] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869668#comment-16869668 ] Filipp Gunbin commented on LOG4J2-2636: --- Makes sense. > No default value for mdcId in

[jira] [Commented] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869666#comment-16869666 ] Filipp Gunbin commented on LOG4J2-2636: --- [~rgoers] what about the second line the patch changes?

[jira] [Issue Comment Deleted] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filipp Gunbin updated LOG4J2-2636: -- Comment: was deleted (was: [~rgoers] what about the second line the patch changes? According

[jira] [Commented] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869658#comment-16869658 ] Ralph Goers commented on LOG4J2-2636: - The suggested patch is wrong. The id field is the default

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

See

[jira] [Commented] (LOG4J2-2591) RollingFileAppender don't append log file after restart service.

[ https://issues.apache.org/jira/browse/LOG4J2-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869550#comment-16869550 ] Davide Martusciello commented on LOG4J2-2591: - same problem to me! With CronTriggeringPolicy

[jira] [Commented] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869546#comment-16869546 ] Filipp Gunbin commented on LOG4J2-2636: --- Yes, that's what I meant about 3rd point, but I really

Jenkins build is unstable: Log4j 2 3.x #431

See

[jira] [Work logged] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?focusedWorklogId=264687=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-264687 ] ASF GitHub Bot logged work on LOG4J2-1301: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on issue #25: LOG4J2-1301 added optionalMonitorFiles attribute for automatic reconf…

rgoers commented on issue #25: LOG4J2-1301 added optionalMonitorFiles attribute for automatic reconf… URL: https://github.com/apache/logging-log4j2/pull/25#issuecomment-504451158 In light of LOG4J2-494 and LOG4J2-913 this PR now has conflicts that would have to be resolved. This

[jira] [Commented] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869536#comment-16869536 ] Ralph Goers commented on LOG4J2-1301: - Actually, CompositeConfiguration was implemented with

Jenkins build is unstable: Log4j 2 2.x #3934

See

[jira] [Closed] (LOG4J2-2638) Add and use method org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2638. Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.12.0

[jira] [Comment Edited] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869510#comment-16869510 ] Gary Gregory edited comment on LOG4J2-2636 at 6/21/19 2:09 PM: --- How about:

[jira] [Commented] (LOG4J2-2636) No default value for mdcId in SyslogAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869510#comment-16869510 ] Gary Gregory commented on LOG4J2-2636: -- How about: {code:diff} diff --git

[jira] [Commented] (LOG4J2-2634) AsyncLogger method bytecode should be reduced to 35 bytes for fast inlining

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

[jira] [Commented] (LOG4J2-2634) AsyncLogger method bytecode should be reduced to 35 bytes for fast inlining

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

[jira] [Created] (LOG4J2-2638) Add and use method org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler subclasses

Gary Gregory created LOG4J2-2638: Summary: Add and use method org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler subclasses Key: LOG4J2-2638 URL:

[jira] [Commented] (LOG4J2-2637) log4j-over-slf4j.jar and slf4j-log4j12.jar

[ https://issues.apache.org/jira/browse/LOG4J2-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869469#comment-16869469 ] james601232 commented on LOG4J2-2637: - fine. thank u so much > log4j-over-slf4j.jar and

[jira] [Closed] (LOG4J2-2405) Better handling of %highlight pattern when using jul-bridge

[ https://issues.apache.org/jira/browse/LOG4J2-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Herrn closed LOG4J2-2405. --- > Better handling of %highlight pattern when using jul-bridge >

[jira] [Closed] (LOG4J2-2403) Allow zero padding the counter of a RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Herrn closed LOG4J2-2403. --- > Allow zero padding the counter of a RollingFileAppender >

[GitHub] [logging-log4j2] fgunbin commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy

fgunbin commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy URL: https://github.com/apache/logging-log4j2/pull/283#issuecomment-504414546 Pushed the update, please check. There's Travis failure somewhere in Log4j Sample Configuration Service

[jira] [Resolved] (LOG4J2-2637) log4j-over-slf4j.jar and slf4j-log4j12.jar

[ https://issues.apache.org/jira/browse/LOG4J2-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2637. - Resolution: Invalid The jars you are mentioning are part of slf4j, not Log4J. Please ask on

[jira] [Closed] (LOG4J2-2637) log4j-over-slf4j.jar and slf4j-log4j12.jar

[ https://issues.apache.org/jira/browse/LOG4J2-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2637. --- > log4j-over-slf4j.jar and slf4j-log4j12.jar > --- > >

[GitHub] [logging-log4j2] remkop commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy

remkop commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy URL: https://github.com/apache/logging-log4j2/pull/283#issuecomment-504393658 Makes sense. This is an automated message from

[GitHub] [logging-log4j2] carterkozak commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy

carterkozak commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy URL: https://github.com/apache/logging-log4j2/pull/283#issuecomment-504390983 I think we can use the enum `name()` from `ThreadNameCachingStrategy` instead of defining new constants.

[GitHub] [logging-log4j2] remkop commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy

remkop commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy URL: https://github.com/apache/logging-log4j2/pull/283#issuecomment-504383978 @fgunbin if these are only locally used I would prefer not to define them in `Constants` but just define them

[jira] [Created] (LOG4J2-2637) log4j-over-slf4j.jar and slf4j-log4j12.jar

james601232 created LOG4J2-2637: --- Summary: log4j-over-slf4j.jar and slf4j-log4j12.jar Key: LOG4J2-2637 URL: https://issues.apache.org/jira/browse/LOG4J2-2637 Project: Log4j 2 Issue Type:

[GitHub] [logging-log4j2] fgunbin commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy

fgunbin commented on issue #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy URL: https://github.com/apache/logging-log4j2/pull/283#issuecomment-504364852 @garydgregory No problem, though I viewed duplication in test file as a kind of test that strings are right.

[jira] [Comment Edited] (LOG4J2-2635) Wrong java.version check in ThreadNameCachingStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869319#comment-16869319 ] Filipp Gunbin edited comment on LOG4J2-2635 at 6/21/19 9:21 AM: Yes,

[jira] [Comment Edited] (LOG4J2-2635) Wrong java.version check in ThreadNameCachingStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869319#comment-16869319 ] Filipp Gunbin edited comment on LOG4J2-2635 at 6/21/19 9:21 AM: Yes,

[jira] [Comment Edited] (LOG4J2-2635) Wrong java.version check in ThreadNameCachingStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869319#comment-16869319 ] Filipp Gunbin edited comment on LOG4J2-2635 at 6/21/19 9:21 AM: Yes,

[jira] [Comment Edited] (LOG4J2-2635) Wrong java.version check in ThreadNameCachingStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869319#comment-16869319 ] Filipp Gunbin edited comment on LOG4J2-2635 at 6/21/19 9:20 AM: Yes,

[jira] [Commented] (LOG4J2-2635) Wrong java.version check in ThreadNameCachingStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869319#comment-16869319 ] Filipp Gunbin commented on LOG4J2-2635: --- Yes, here it is

[GitHub] [logging-log4j2] fgunbin opened a new pull request #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy

fgunbin opened a new pull request #283: LOG4J-2635: Fix java.version check in ThreadNameCachingStrategy URL: https://github.com/apache/logging-log4j2/pull/283 This is an automated message from the Apache Git Service. To