> > 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?!
Strange...I'm not making this up you know. It happens every single time I try it, and before I applied my little workaround, Kannel would get CPU-hungry several times per day - now it only happens once a week and we have approx. 1000 times the traffic we had back then? Could it be a platform dependant problem (sounds rather unlikely but...)? cheers, Frederik Ammitzb�ll Unwire Vestergade 12A, 3. 1456 K�benhavn K Tlf.: +45 33 33 08 70 Mobil: +45 27 11 99 99 Fax : +45 33 33 09 70 Web: www.unwire.dk
