You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by "Thorsten Schöning (JIRA)" <lo...@logging.apache.org> on 2014/02/10 14:19:21 UTC

[jira] [Resolved] (LOGCXX-305) Property/DOMConfigurator::configureAndWatch can continue to run after APR termination

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

Thorsten Schöning resolved LOGCXX-305.
--------------------------------------

    Resolution: Fixed

I applied the C patch to trunk, simply because it looked OK and we want as much patches as possible in the next release.

> Property/DOMConfigurator::configureAndWatch can continue to run after APR termination
> -------------------------------------------------------------------------------------
>
>                 Key: LOGCXX-305
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-305
>             Project: Log4cxx
>          Issue Type: Bug
>            Reporter: Curt Arnold
>            Assignee: Curt Arnold
>         Attachments: LOGCXX-305.patch, LOGCXX-305B.patch, LOGCXX-305C.patch.txt
>
>
> The configureAndWatch methods launch a thread to monitor whether a configuration file has changed.  Once launched, there is no attempt to reclaim or cleanly shut down the thread when the application exits.  Depending on the circumstance, this can delay the programs exit or cause a crash.
> The attached patch attempts to shutdown the watchdog thread when the supporting APR pool is being destroyed as part of the APR shutdown sequence.  Unfortunately, the patch as it stands will result in a warning about double freed memory when running the modified trivial test program.
> The changes to trivial.cpp are not intended to be committed, but provide a sample for testing configureAndWatch.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)