Hi, Paul.
Paul Keogh wrote:
After browsing you can select from menu something like 'Quit
browsing' and
user agent correctly sends disconnect event. But I suspect if
you simply
press HangUp button, UserAgent simply go out without disconnect event.
(I checked it at least with some phones).
And users mostly end its sessions by this way.
So if you have heavy load it becomes the problem.
For example our WAP gateway grows approximatly at 100MB every day.
So I agree that this is phone problem, but I think kannel must
handle it someway.
I have also seen quite different behaviours from devices and disconnects
and agree with what you say. I also suspect that this may cause resource
problems with sockets not being closed.
Ok, if we talk about not closed sockets than there is problem in http library.
See in http.c :
/* XXX re-implement socket pools, with idle connection killing to
save sockets */
Every http request to new host create socket and didn't close it even
if remote side did it.
There is no any check for it. And only when gateway
will try to reuse it, socket will be closed and http will open new socket to
this host.
So if system has limit for opened socket it will be exceeded sooner or later.
Simplest solution for it - periodically check pool and destroy all
closed socket.
--
Vjacheslav Chekushin mailto:[EMAIL PROTECTED]
Latvian Mobile Phone Company http://www.lmt.lv
