25 Jun
2007
25 Jun
'07
11:22 a.m.
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: Monday, June 25, 2007 9:28 AM
To: Papadopoulos Georgios
Cc: Bogdan-Andrei Iancu; users(a)openser.org
Subject: Re: [OpenSER-Users] RE: [Users] out of memory - please help
Papadopoulos Georgios wrote:
Then how do you explain that only the first child ran out of memory?
Disclaimer
The information in this e-mail and any attachments is confidential. It is intended solely
for the attention and use of the named addressee(s). If you are not the intended
recipient, or person responsible for delivering this information to the intended
recipient, please notify the sender immediately. Unless you are the intended recipient or
his/her representative you are not authorized to, and must not, read, copy, distribute,
use or retain this message or any part of it. E-mail transmission cannot be guaranteed to
be secure or error-free as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.
Why did this only appear on the first receiver
child? I
would expect
that all children receive an equal amount of
traffic so they should
all run out of memory more or less at the same time. Except
if when a
message is received, Openser finds the first
available
child and does
this by trying child 1,2,3... Is this the case?
The distribution between the UDP listener threads is not done
by openser but by the OS. openser will open port 5060 and
then fork the process "children=..." times. Then, all
processes will read from the same port.