3 Mar
2020
3 Mar
'20
11:41 a.m.
Looks like something odd happened there. Is the timer process somehow
stuck? Any jump of the system clock? Virtual machine frozen somehow? Or
the transactions remained hooked in some callback, not releasing the
reference counter.
The rpc command tm.clean is like a last resort option when dealing with
an unexpected situation that messed up the timer process, otherwise the
transactions should be cleaned as they are expired or terminated because
of final response sent upstream, with a delay of 5 seconds (default value).
Cheers,
Daniel
On 03.03.20 02:00, Juha Heinanen wrote:
What kind of delay there is on cleaning of an expired
transaction? I'm
asking, since tm.clean released lots of shm.
-- Juha
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com