[erlang-questions] gen_fsm timer getting canceled/never firing
Jesper Louis Andersen
Wed Dec 17 17:44:40 CET 2014
On Wed, Dec 17, 2014 at 5:26 PM, Matthew Evans <>
> Is it possible that timers could get canceled for some unknown reason?
Such a timer is cancelled if *any* message arrives or another event
happens. The callback timeouts only trigger if no other event happens in
the window. For a more surefire way, see gen_fsm:start_timer/2 which runs
on the internal erlang timer and doesn't have this problem. You often see
the call-back timers missed due to someone altering the FSMs behaviour in a
way such that it does not trigger. Or if the system suddenly experiences
more load so the timers won't trigger anymore.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions