[jira] [Commented] (LOG4J2-2562) RollingFileManager create wrong file name with TimeBasedTriggeringPolicy

[ https://issues.apache.org/jira/browse/LOG4J2-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784125#comment-16784125 ] finalmachine commented on LOG4J2-2562: -- I test more code. I find the app.log create

[jira] [Commented] (LOG4J2-2562) RollingFileManager create wrong file name with TimeBasedTriggeringPolicy

[ https://issues.apache.org/jira/browse/LOG4J2-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784105#comment-16784105 ] finalmachine commented on LOG4J2-2562: -- I change time use windows gui tool bar > R

[jira] [Created] (LOG4J2-2562) RollingFileManager create wrong file name with TimeBasedTriggeringPolicy

finalmachine created LOG4J2-2562: Summary: RollingFileManager create wrong file name with TimeBasedTriggeringPolicy Key: LOG4J2-2562 URL: https://issues.apache.org/jira/browse/LOG4J2-2562 Project: Log

[jira] [Commented] (LOG4J2-913) Allow to load log4j2 configuration from a centralized repository, like a database or a webservice

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

Jenkins build is back to normal : Log4j 2 3.x #368

See

[jira] [Commented] (LOG4J2-913) Allow to load log4j2 configuration from a centralized repository, like a database or a webservice

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

[jira] [Commented] (LOG4J2-2266) Log4j2 throws NoClassDefFoundError in Java 8

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

[jira] [Commented] (LOG4J2-913) Allow to load log4j2 configuration from a centralized repository, like a database or a webservice

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

[jira] [Commented] (LOG4J2-913) Allow to load log4j2 configuration from a centralized repository, like a database or a webservice

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

[jira] [Commented] (LOG4J2-1906) DirectWriteRolloverStrategy not properly creating files

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

[GitHub] [logging-log4j2] rgoers closed pull request #253: Log4 j2 913 - Add support for HTTP/S configuration monitoring. Support Spring Cloud Config

rgoers closed pull request #253: Log4 j2 913 - Add support for HTTP/S configuration monitoring. Support Spring Cloud Config URL: https://github.com/apache/logging-log4j2/pull/253 This is an automated message from the Apache

[jira] [Work logged] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

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

[GitHub] [logging-log4j2] ulrichenslin commented on a change in pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up

ulrichenslin commented on a change in pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up URL: https://github.com/apache/logging-log4j2/pull/260#discussion_r262054233 ## File path: log4j-api/src/test/java/org/apache/logging/log4j/util/ConstantsTest.java

[jira] [Work logged] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

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

[GitHub] [logging-log4j2] cakofony commented on a change in pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up

cakofony commented on a change in pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up URL: https://github.com/apache/logging-log4j2/pull/260#discussion_r262024621 ## File path: log4j-core/src/test/java/org/apache/logging/log4j/core/layout/AbstractStringLa

[jira] [Work logged] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

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

[GitHub] [logging-log4j2] cakofony commented on a change in pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up

cakofony commented on a change in pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up URL: https://github.com/apache/logging-log4j2/pull/260#discussion_r262025574 ## File path: log4j-api/src/test/java/org/apache/logging/log4j/util/ConstantsTest.java

[jira] [Closed] (LOG4J2-2552) Allow access to the backlog state of the disruptor to improve programatic reconfiguration of async appenders.

[ https://issues.apache.org/jira/browse/LOG4J2-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Togher closed LOG4J2-2552. --- Resolution: Information Provided Commemted on PR. Correct use is  RingBufferAdmin admin = ((AsyncL

[jira] [Work logged] (LOG4J2-2552) Allow access to the backlog state of the disruptor to improve programatic reconfiguration of async appenders.

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

[GitHub] [logging-log4j2] ptogher closed pull request #257: LOG4J2-2552 Allow access to the backlog state of the disruptor to improve program…

ptogher closed pull request #257: LOG4J2-2552 Allow access to the backlog state of the disruptor to improve program… URL: https://github.com/apache/logging-log4j2/pull/257 This is an automated message from the Apache Git Ser

[jira] [Work logged] (LOG4J2-2552) Allow access to the backlog state of the disruptor to improve programatic reconfiguration of async appenders.

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

[GitHub] [logging-log4j2] ptogher commented on issue #257: LOG4J2-2552 Allow access to the backlog state of the disruptor to improve program…

ptogher commented on issue #257: LOG4J2-2552 Allow access to the backlog state of the disruptor to improve program… URL: https://github.com/apache/logging-log4j2/pull/257#issuecomment-469190129 Ooh, many thanks, That's really useful. I missed this when i was looking for a solution. Complet