You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/09 22:10:59 UTC

[jira] [Commented] (COUCHDB-3102) The xxx_config_listener doesn't restart after a failure

    [ https://issues.apache.org/jira/browse/COUCHDB-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652197#comment-15652197 ] 

ASF GitHub Bot commented on COUCHDB-3102:
-----------------------------------------

Github user iilyak closed the pull request at:

    https://github.com/apache/couchdb-couch-log/pull/14


> The xxx_config_listener doesn't restart after a failure
> -------------------------------------------------------
>
>                 Key: COUCHDB-3102
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3102
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: ILYA
>
> The [config_listener_mon|https://github.com/apache/couchdb-config/blob/master/src/config_listener_mon.erl#L44] monitors the caller. 
> However in lots of places we use [following pattern|https://github.com/apache/couchdb-chttpd/blob/master/src/chttpd_config_listener.erl#L45:L49]
> {code}
> handle_config_terminate(_Server, _Reason, State) ->
>     spawn(fun() ->
>         timer:sleep(5000),
>         config:listen_for_changes(?MODULE, State)
>     end).
> {code}
> In this case the spawned fun exits right after the monitor has been established.
> Which means config_listener_mon would terminate. Effectively removing event handler from config_event process (gen_event event manager).
> When this happen any further configuration changes get unnoticed by processes.



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