[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Fix Version/s: boot-1.0-alpha1 > log4j-boot pom modules for dependency managem

[jira] [Closed] (LOG4J2-1778) Add logging-log4j-boot git repo

[ https://issues.apache.org/jira/browse/LOG4J2-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-1778. --- Resolution: Fixed Fix Version/s: boot-1.0-alpha1 Marking with fix version. > Add logg

[jira] [Updated] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-boot module test suites

[ https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1777: Fix Version/s: boot-1.0-alpha1 > Add JUnit categories to integration tests for use in log4j-b

[jira] [Updated] (LOG4J2-1783) Add site config for Log4j Boot

[ https://issues.apache.org/jira/browse/LOG4J2-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1783: Fix Version/s: boot-1.0-alpha1 > Add site config for Log4j B

[jira] [Commented] (LOG4J2-1783) Add site config for Log4j Boot

[ https://issues.apache.org/jira/browse/LOG4J2-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823031#comment-15823031 ] Matt Sicker commented on LOG4J2-1783: - I've added a minimal site config so far. Still need

[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=15823030#comment-15823030 ] Charles Hache commented on LOG4J2-1784: --- Thanks for the prompt replies! Changing the configuration

[jira] [Comment Edited] (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=15823016#comment-15823016 ] Ralph Goers edited comment on LOG4J2-1784 at 1/15/17 3:25 AM: -- Actually

[jira] [Assigned] (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:all-tabpanel ] Ralph Goers reassigned LOG4J2-1784: --- Assignee: Ralph Goers > Large values for max in DefaultRolloverStrategy blocks applicat

[jira] [Updated] (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:all-tabpanel ] Ralph Goers updated LOG4J2-1784: Issue Type: Improvement (was: Bug) > Large values for max in DefaultRolloverStrategy blo

[jira] [Closed] (LOG4J2-1786) ConfigurationScheduler should preserve interrupt flag during stop

[ https://issues.apache.org/jira/browse/LOG4J2-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1786. --- Resolution: Fixed Fixed in master in commit 1f06ca4. > ConfigurationScheduler should prese

[jira] [Updated] (LOG4J2-1786) ConfigurationScheduler should preserve interrupt flag during stop

[ https://issues.apache.org/jira/browse/LOG4J2-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1786: Summary: ConfigurationScheduler should preserve interrupt flag during stop

[jira] [Created] (LOG4J2-1786) ConfigurationScheduler should preserve interrupt flag during shutdown

Remko Popma created LOG4J2-1786: --- Summary: ConfigurationScheduler should preserve interrupt flag during shutdown Key: LOG4J2-1786 URL: https://issues.apache.org/jira/browse/LOG4J2-1786 Project: Log4j 2

[jira] [Created] (LOG4J2-1785) Add Spring Boot integration to Log4j Boot

Matt Sicker created LOG4J2-1785: --- Summary: Add Spring Boot integration to Log4j Boot Key: LOG4J2-1785 URL: https://issues.apache.org/jira/browse/LOG4J2-1785 Project: Log4j 2 Issue Type: New

[jira] [Comment Edited] (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=15822991#comment-15822991 ] Remko Popma edited comment on LOG4J2-1784 at 1/14/17 11:32 PM: --- During

[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=15822991#comment-15822991 ] Remko Popma commented on LOG4J2-1784: - During the rollover Log4j2 will log what it's doing

[jira] [Comment Edited] (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=15822945#comment-15822945 ] Charles Hache edited comment on LOG4J2-1784 at 1/14/17 8:29 PM: My config

[jira] [Comment Edited] (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=15822945#comment-15822945 ] Charles Hache edited comment on LOG4J2-1784 at 1/14/17 8:28 PM: My config

[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=15822945#comment-15822945 ] Charles Hache commented on LOG4J2-1784: --- My config might be useful

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

Charles Hache created LOG4J2-1784: - Summary: Large values for max in DefaultRolloverStrategy blocks application Key: LOG4J2-1784 URL: https://issues.apache.org/jira/browse/LOG4J2-1784 Project: Log4j

[jira] [Created] (LOG4J2-1783) Add site config for Log4j Boot

Matt Sicker created LOG4J2-1783: --- Summary: Add site config for Log4j Boot Key: LOG4J2-1783 URL: https://issues.apache.org/jira/browse/LOG4J2-1783 Project: Log4j 2 Issue Type: Documentation

[jira] [Created] (LOG4J2-1782) Upgrade to JCTools from 1.2.1 to 2.0.1

Matt Sicker created LOG4J2-1782: --- Summary: Upgrade to JCTools from 1.2.1 to 2.0.1 Key: LOG4J2-1782 URL: https://issues.apache.org/jira/browse/LOG4J2-1782 Project: Log4j 2 Issue Type

[jira] [Closed] (LOG4J2-1781) Update Conversant Disruptor from 1.2.7 to 1.2.10

[ https://issues.apache.org/jira/browse/LOG4J2-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-1781. --- Resolution: Fixed Added to master. > Update Conversant Disruptor from 1.2.7 to 1.2

[jira] [Created] (LOG4J2-1781) Update Conversant Disruptor from 1.2.7 to 1.2.10

Matt Sicker created LOG4J2-1781: --- Summary: Update Conversant Disruptor from 1.2.7 to 1.2.10 Key: LOG4J2-1781 URL: https://issues.apache.org/jira/browse/LOG4J2-1781 Project: Log4j 2 Issue Type

[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Description: This is the main feature for the Log4j Boot epic (LOG4J2-1775). {code} groupId

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821805#comment-15821805 ] gpolaert commented on LOG4J2-1694: -- Hello, IMO, allow user to add `` is really useful. So, is someone

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820805#comment-15820805 ] Mikael Ståldal commented on LOG4J2-1748: I have a solution for this and LOG4J-1780, please review

[jira] [Resolved] (LOG4J2-1780) Eliminate the use of the ExecutorServices in the LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1780. Resolution: Fixed Fix Version/s: 2.8 See branch LOG4J2-1748and1780-remove

[jira] [Updated] (LOG4J2-1780) Eliminate the use of the ExecutorServices in the LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1780: --- Summary: Eliminate the use of the ExecutorServices in the LoggerContext (was: LoggerContext

[jira] [Assigned] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1780: -- Assignee: Mikael Ståldal > LoggerContext does not shut down old executor servi

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820759#comment-15820759 ] Mikael Ståldal commented on LOG4J2-1748: I don't think it is that complicated to keep track

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820692#comment-15820692 ] Remko Popma commented on LOG4J2-1748: - I disagree. We've seen problems in the past when the Async

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820630#comment-15820630 ] Mikael Ståldal commented on LOG4J2-1748: The root cause of the problem is using non-daemon

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820604#comment-15820604 ] Mikael Ståldal commented on LOG4J2-1748: Yes, I agree. But while waiting for us to fix

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

[ https://issues.apache.org/jira/browse/LOG4J2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820397#comment-15820397 ] Travis Spencer commented on LOG4J2-1381: While this area of the documentation is being updated

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820023#comment-15820023 ] Ralph Goers commented on LOG4J2-1748: - I have no problem using the ThreadFactory to create the thread

[jira] [Comment Edited] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819620#comment-15819620 ] Remko Popma edited comment on LOG4J2-1748 at 1/12/17 12:52 AM: --- If rollover

[jira] [Comment Edited] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819620#comment-15819620 ] Remko Popma edited comment on LOG4J2-1748 at 1/12/17 12:49 AM: --- If rollover

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819620#comment-15819620 ] Remko Popma commented on LOG4J2-1748: - It would be nice if the shutdown hook would be able to print

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819604#comment-15819604 ] Remko Popma commented on LOG4J2-1748: - Probably best to have only one ExecutorService. Naming-wise

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819347#comment-15819347 ] Ralph Goers commented on LOG4J2-1780: - I don't see the problem. It is owned by the Configuration so

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819341#comment-15819341 ] Ralph Goers commented on LOG4J2-1748: - We have an ExecutorService. It is called

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819340#comment-15819340 ] Gary Gregory commented on LOG4J2-1780: -- Maybe the {{ConfigurationScheduler}} is misnamed because

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819309#comment-15819309 ] Ralph Goers commented on LOG4J2-1780: - The LoggerContext should not have any ExecutorServices

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819275#comment-15819275 ] Ralph Goers commented on LOG4J2-1748: - Again, lets just get rid of these ExecutorService instances

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819273#comment-15819273 ] Ralph Goers commented on LOG4J2-1748: - I don't think that is a great recommendation. > RollingF

[jira] [Comment Edited] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819273#comment-15819273 ] Ralph Goers edited comment on LOG4J2-1748 at 1/11/17 9:44 PM: -- I don't think

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819271#comment-15819271 ] Ralph Goers commented on LOG4J2-1748: - I don't know why those two ThreadPoolExecutors were added

[jira] [Commented] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819217#comment-15819217 ] Mikael Ståldal commented on LOG4J2-1776: Why do we have logback here? > log4j-boot pom modu

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819168#comment-15819168 ] Mikael Ståldal commented on LOG4J2-1780: Otherwise, an easy solution would be to create

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819147#comment-15819147 ] Mikael Ståldal commented on LOG4J2-1748: But I think the proper way to handle this is to have our

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816578#comment-15816578 ] Gary Gregory commented on LOG4J2-1748: -- Yep, IIRC, that is why I did it that way. > RollingF

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816488#comment-15816488 ] Remko Popma commented on LOG4J2-1748: - I believe (I could be wrong) that the non-daemon thread

[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=15816297#comment-15816297 ] Ralph Goers commented on LOG4J2-1640: - Yes, you would need to re-clone and re-build. If you want

[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=15816237#comment-15816237 ] Chris McGee commented on LOG4J2-1640: - Wow, a lot of new info to take in. I don't fully understand

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816238#comment-15816238 ] Gary Gregory commented on LOG4J2-1780: -- What I think we need to consider here is if reconfiguring

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816212#comment-15816212 ] Mikael Ståldal commented on LOG4J2-1780: Ping [~garydgregory] > LoggerContext does not shut d

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816208#comment-15816208 ] Mikael Ståldal commented on LOG4J2-1748: Created a bug for the failure to shut down old

[jira] [Created] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

Mikael Ståldal created LOG4J2-1780: -- Summary: LoggerContext does not shut down old executor services when creating new ones during reconfiguration Key: LOG4J2-1780 URL: https://issues.apache.org/jira/browse

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816150#comment-15816150 ] Mikael Ståldal commented on LOG4J2-1748: I am not sure that it will be dangerous to use a daemon

[jira] [Closed] (LOG4J2-1762) Add Builder to GelfLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1762. -- > Add Builder to GelfLayout > - > > Key:

[jira] [Closed] (LOG4J2-1769) JsonLayout Throwing Exceptions And Producing Broken Logs

[ https://issues.apache.org/jira/browse/LOG4J2-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Goodin closed LOG4J2-1769. -- This is indeed fixed in the 2.7.1 SNAPSHOT. > JsonLayout Throwing Exceptions And Producing Bro

[jira] [Commented] (LOG4J2-1769) JsonLayout Throwing Exceptions And Producing Broken Logs

[ https://issues.apache.org/jira/browse/LOG4J2-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815651#comment-15815651 ] Brandon Goodin commented on LOG4J2-1769: I tested against 2.7.1-SNAPSHOT on January 10th (https

[jira] [Closed] (LOG4J2-1779) AsyncLogger does not lookup properties

[ https://issues.apache.org/jira/browse/LOG4J2-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1779. --- > AsyncLogger does not lookup propert

[jira] [Resolved] (LOG4J2-1779) AsyncLogger does not lookup properties

[ https://issues.apache.org/jira/browse/LOG4J2-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1779. - Resolution: Fixed Fixed in commit a686a4e. > AsyncLogger does not lookup propert

[jira] [Created] (LOG4J2-1779) AsyncLogger does not lookup properties

Remko Popma created LOG4J2-1779: --- Summary: AsyncLogger does not lookup properties Key: LOG4J2-1779 URL: https://issues.apache.org/jira/browse/LOG4J2-1779 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815008#comment-15815008 ] Alexander K. commented on LOG4J2-1724: -- It works as expected. Thanks. > Using variab

[jira] [Closed] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander K. closed LOG4J2-1724. > Using variables in GelfLayout's additional fields at runt

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814716#comment-15814716 ] Mikael Ståldal commented on LOG4J2-1748: After looking more closely at this, I think it actually

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814711#comment-15814711 ] Mikael Ståldal commented on LOG4J2-1748: A simple workaround is to add System.exit(0) at the end

[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Description: This is the main feature for the Log4j Boot epic (LOG4J2-1775). {code} groupId

[jira] [Closed] (LOG4J2-1778) Add logging-log4j-boot git repo

[ https://issues.apache.org/jira/browse/LOG4J2-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-1778. --- Resolution: Fixed https://git-wip-us.apache.org/repos/asf/logging-log4j-boot.git > Add logg

[jira] [Updated] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-boot module test suites

[ https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1777: Description: Add JUnit {{@Category}} [annotations|https://github.com/junit-team/junit4/wiki

[jira] [Updated] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-boot module test suites

[ https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1777: Summary: Add JUnit categories to integration tests for use in log4j-boot module test suites

[jira] [Assigned] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-starter module test suites

[ https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-1777: --- Assignee: Matt Sicker > Add JUnit categories to integration tests for use in log4j-star

[jira] [Created] (LOG4J2-1778) Add logging-log4j-boot git repo

Matt Sicker created LOG4J2-1778: --- Summary: Add logging-log4j-boot git repo Key: LOG4J2-1778 URL: https://issues.apache.org/jira/browse/LOG4J2-1778 Project: Log4j 2 Issue Type: New Git Repo

[jira] [Updated] (LOG4J2-1775) Log4j Boot modules for easy dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1775: Summary: Log4j Boot modules for easy dependency management (was: Add boot pom files

[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Description: This is the main feature for the Log4j Boot epic (LOG4J2-1775). {code} groupId

[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Summary: log4j-boot pom modules for dependency management (was: log4j-starter pom modules

[jira] [Updated] (LOG4J2-1775) Add boot pom files for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1775: - Summary: Add boot pom files for dependency management (was: Add starter pom files

[jira] [Updated] (LOG4J2-1775) Add starter pom files for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1775: Epic Name: Log4j Boot (was: Log4j Starters) > Add starter pom files for dependency managem

[jira] [Commented] (LOG4J2-1776) log4j-starter pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813291#comment-15813291 ] Ralph Goers commented on LOG4J2-1776: - +1 for log4j-boot. > log4j-starter pom modules for depende

[jira] [Commented] (LOG4J2-1776) log4j-starter pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813255#comment-15813255 ] Matt Sicker commented on LOG4J2-1776: - For brevity's sake, "log4j-boot" is even be

[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=15813191#comment-15813191 ] Gary Gregory commented on LOG4J2-1768: -- Please do try 2.7. Gary > MDC.clear() is broken in Lo

[jira] [Commented] (LOG4J2-1776) log4j-starter pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813100#comment-15813100 ] Gary Gregory commented on LOG4J2-1776: -- Would the prefix "log4j-start" also be accept

[jira] [Commented] (LOG4J2-1713) Allow for more general serialization of Log4j2 configurations

[ https://issues.apache.org/jira/browse/LOG4J2-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812998#comment-15812998 ] Kurt Seidel commented on LOG4J2-1713: - Thanks for the reply. I think that answers my question. I am

[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=15812875#comment-15812875 ] Matt Sicker commented on LOG4J2-1640: - Oh ok, got it. > RollingFileAppen

[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=15812841#comment-15812841 ] Ralph Goers commented on LOG4J2-1640: - No. As I said, System.nanotime() is relative to the time

[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=15812770#comment-15812770 ] Matt Sicker commented on LOG4J2-1640: - Couldn't you use {{new Date(TimeUnit.NANOS.toMillis(nanoValue

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

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1640. - Resolution: Fixed Fix Version/s: 2.8 Please verify and close. > RollingFileAppen

[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=15812045#comment-15812045 ] Ralph Goers commented on LOG4J2-1640: - So it turns out that the ScheduledExecutorServices in Java use

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811361#comment-15811361 ] Remko Popma commented on LOG4J2-1724: - Nice! > Using variables in GelfLayout's additional fie

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811186#comment-15811186 ] Remko Popma commented on LOG4J2-1748: - I think it's a good idea to use

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811165#comment-15811165 ] Remko Popma commented on LOG4J2-1748: - ... and another good catch! Two actually

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811123#comment-15811123 ] Mikael Ståldal commented on LOG4J2-1724: OK. I managed to keep it gc-free with additional fields

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811075#comment-15811075 ] Mikael Ståldal commented on LOG4J2-1748: Anyway, we could change "shutdownTimeout" t

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811073#comment-15811073 ] Mikael Ståldal commented on LOG4J2-1748: I don't really understand why we can't use

[jira] [Created] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-starter module test suites

Matt Sicker created LOG4J2-1777: --- Summary: Add JUnit categories to integration tests for use in log4j-starter module test suites Key: LOG4J2-1777 URL: https://issues.apache.org/jira/browse/LOG4J2-1777

[jira] [Created] (LOG4J2-1776) log4j-starter pom modules for dependency management

Matt Sicker created LOG4J2-1776: --- Summary: log4j-starter pom modules for dependency management Key: LOG4J2-1776 URL: https://issues.apache.org/jira/browse/LOG4J2-1776 Project: Log4j 2 Issue

[jira] [Updated] (LOG4J2-1775) Add starter pom files for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1775: Description: Create what is essentially Log4j Boot for adding necessary dependencies to support

[jira] [Created] (LOG4J2-1775) Add starter pom files for dependency management

Matt Sicker created LOG4J2-1775: --- Summary: Add starter pom files for dependency management Key: LOG4J2-1775 URL: https://issues.apache.org/jira/browse/LOG4J2-1775 Project: Log4j 2 Issue Type

<    5   6   7   8   9   10   11   12   13   14   >