[erlang-questions] "simple_one_for_one" supervisor childs termination problem
zabrane Mikael
zabrane3@REDACTED
Tue Nov 30 14:20:07 CET 2010
Maybe that's the reason. Anyway, I'm pretty happy with gen_server2 as
we're using it for a while in production (we moved all our code from gen_server
togen_server2).
Thanks Lukas
--
Regards
Zabrane
2010/11/30 Lukas Larsson <garazdawi@REDACTED>:
> might be gen_server2 which does not play nice with supervisor, using OTP's
> supervisor and gen_server the terminate call works as it should.
>
> Lukas
>
> On Tue, Nov 30, 2010 at 2:05 PM, zabrane Mikael <zabrane3@REDACTED> wrote:
>>
>> Hi Matthew,
>>
>> It works like a charm with supervisor2.
>> You save my day ;-) Thousand thanks.
>>
>> --
>> Regards
>> Zabrane
>>
>> 2010/11/30 Matthew Sackman <matthew@REDACTED>:
>> > On Tue, Nov 30, 2010 at 01:40:09PM +0100, zabrane Mikael wrote:
>> >> I forgot to mention that I'm already traping exit in "foo_srv.erl":
>> >> %% --- gen server callbacks
>> >> init(Args) ->
>> >> process_flag(trap_exit, true),
>> >> {ok, Args}.
>> >>
>> >> Even with that, the worker process never get the "shutdown" EXIT
>> >> message.
>> >
>> > That's odd then. That should only happen if there's a
>> > brutal_kill/exit(kill) going on.
>> >
>> > Matthew
>> >
>> > ________________________________________________________________
>> > erlang-questions (at) erlang.org mailing list.
>> > See http://www.erlang.org/faq.html
>> > To unsubscribe; mailto:erlang-questions-unsubscribe@REDACTED
>> >
>> >
>>
>> ________________________________________________________________
>> erlang-questions (at) erlang.org mailing list.
>> See http://www.erlang.org/faq.html
>> To unsubscribe; mailto:erlang-questions-unsubscribe@REDACTED
>>
>
>
More information about the erlang-questions
mailing list