[erlang-questions] timer server timeout

johan munk <>
Mon Apr 26 10:31:32 CEST 2010


But attaching to a production node and periodically asking a gen_server for
it's state for raw monitoring of it is now potentially causing that server
to malfunction.
I would say that at least calls for an NB in doc somewhere.

On Mon, Apr 26, 2010 at 10:19 AM, Kenneth Lundin

> This is not a known issue.
> After a quick glance I agree with you that a sys:get_status call to
> the timer_server or any other
> "gen_server" using the gen_server timeout feature can disturb the
> timing either by delaying
> the timeout message or by not letting any timeout message to be sent.
> I will put this on the list of things to  look at.
> It is whoever very unlikely that this happens in normal operation
> since there is no reason to call
> sys:get_status other than for debugging purposes.
> I have never heard of any real problems caused by this.
> /Kenneth  Erlang/OTP Ericsson
> On Wed, Apr 21, 2010 at 10:05 PM, johan munk <> wrote:
> > Following the control flow in the gen_server, sys, and timer modules I
> see
> > this:
> > Calling sys:get_status(timer_server) will "reset" the "after time" in the
> > loop function of gen_server. As the timer server uses that time to get a
> > timeout if no other messages are received, one can potentially cause
> timers
> > to never trigger.
> > Is this a known issue/feature?
> >
> > /JM
> >

More information about the erlang-questions mailing list