You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "ILYA (JIRA)" <ji...@apache.org> on 2016/08/12 15:48:20 UTC
[jira] [Created] (COUCHDB-3102) The xxx_config_listener doesn't
restart after a failure
ILYA created COUCHDB-3102:
-----------------------------
Summary: 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)