Re: Deadlocking application_controller using init:stop/1, 2
Siri Hansen <[email protected]>
| Newsgroups | gmane.comp.lang.erlang.bugs |
|---|---|
| Message-ID | <CAGqERUGNPYzGA6ZU+=XiE3jwi8qzT2p6JDvVT+G6XOWOd-n+vA@mail.gmail.com> |
Thanks for the additional information, Magnus! We will discuss this a bit more in the team before proceeding. Regards /siri 2014-09-09 11:38 GMT+02:00 Magnus Ottenklinger < [email protected]>: > Hey Siri, > > sorry for taking so long to reply. > > Our system takes quite some time starting up (around one minute). While > this is being done, multiple applications are started, each with a > supervisor tree. Within those supervisor trees, processes might start other > OTP applications, such as ssl. > > The init:stop() is sent to the VM by our /etc/init.d script. If e.g. an > error is detected during the startup phase, and we want to stop the node, > the described deadlock appears, rendering the system unstoppable (in a > clean way). > > Regards, Magnus > _______________________________________________ erlang-bugs mailing list [email protected] http://erlang.org/mailman/listinfo/erlang-bugs