Frederik Ammitzbøll schrieb:
See below (sent in July):
---
On a different note I believe to have located the source of CPU-hungry
boxes. The problem lies in Kannel's handling of HTTP 1.1 requests. Try using
the send-sms interface or the Kannel-admin module from a HTTP 1.1 compliant
browser, leave the browser window open and watch the bearerbox or smsbox go
powerhungry ~1 minute after the request. It happens every time!!
My temporary workaround has been to treat all HTTP-requests as HTTP 1.0 (in
http.c), but this is only a short-term solution as there are important
benefits from using HTTP 1.1.
---
This problem has existed for a long time and has never been fixed.
Unfortunately, while my workaround has severely helped, two simultaneous
HTTP-request to Kannel can sometimes have the same effect.
I tried to reconstruct the HTTP/1.1 based effect you describe using
the admin interface, but could not see any bearerbox's cpu demand
which would lead me to such an assumption?!
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are
