logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LOG4J2-1166) Applications using Log4j-2.5 with monitorInterval never shut down
Date Mon, 19 Oct 2015 01:17:05 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remko Popma closed LOG4J2-1166.
-------------------------------

> Applications using Log4j-2.5 with monitorInterval never shut down
> -----------------------------------------------------------------
>
>                 Key: LOG4J2-1166
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1166
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configurators
>    Affects Versions: 2.5
>            Reporter: Remko Popma
>            Assignee: Remko Popma
>            Priority: Critical
>             Fix For: 2.5
>
>
> The new WatchManager introduced in 2.5 uses a ScheduledThreadPoolExecutor so it can roll
over triggered by a timer event instead of a log event.
> The executor currently uses the standard thread factory, which creates non-daemon threads.
This means that applications that use Log4j 2 and have {{monitorInterval="..."}} in their
configuration will never shut down.
> The fix is to pass a {{DaemonThreadFactory}} to the ScheduledThreadPoolExecutor constructor.
(This also allows us to specify a better name than "pool-1-thread-1".)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message