Thanks you Tracy.

I can see high delays in the response from the database, when this response
time is high, we see this message.
In another hand, any one knows the name of this timer in order to increment
the limit to workaround this issue?

Thanks to all.

GCM.

-----Mensaje original-----
De: serusers-bounces@lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] En nombre de Tracy Lofton
Enviado el: Lunes, 18 de Septiembre de 2006 10:55 a.m.
Para: serusers@lists.iptel.org
Asunto: RE: [Serusers] set_timer caller

Hi,
I have read about this warning happening to only about a handful of others 
before in an archive.  And remembered that it  was noted somewhere about 
this happening to sers using radius servers and radius accounting request.

Also, one of the replies to the issue was something about:

"a race condition in timer processing. A transaction
was detached from the timer list by the timer process which is
processing it for expire even; in the same time, another process was
computing the transaction (maybe a reply was received) and it's trying
to place it back into timer....and this is the race."

I do not know what the solution is to this warning but during these brief 
periods i suppose data is not going back and forth from database/ser, and 
visa-versa so maybe you can try to do some more debugging to determine what 
causes this error.

Tracy

T