29 Mar
2007
29 Mar
'07
12:51 p.m.
I wouldn't deaemonize this problem.
This looks like a combination of errors in the old timer subsystem and TM,
which has been known to cause race conditions and consequently either blocked
functionality or crashes. Fortunately, the race conditions do occur rather
rarely, its frequency can be easily delt with using some restart tools,
and it is certainly just matter of time, till the overhauled timer system
+ tm is ported along with tm from SER to openSER.
-jiri
At 17:27 29/03/2007, T.R. Missner wrote:
Does anyone know what causes this?
set_timer for 1 list called on a "detached" timer -- ignoring
I also see
set_timer for 3 list called on a "detached" timer -- ignoring
When this happens Openser seems to lock up for 10 seconds or so.
--
Jiri Kuthan http://iptel.org/~jiri/
From searching it appears this is caused by a race
but I am not sure what the race is or why this results in an unresponsive openser instance
for multiple seconds.
Transaction expiration racing reply?
Desperately need to understand how this could be triggered so I can get customer to adjust
system.
Any way to adjust?
tried tweaking fr_inv_timer but no joy.
TR
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users