Kannel HTTP MO delivery failing under load
giulio.harding at mnetcorporation.com
Sun Aug 6 10:46:31 CEST 2006
Alexander Malysh wrote:
> It's a bug in smsbox that it didn't limit max allowed http connections.
> The same bug is present in HTTP SMSC module. HTTP was fixed by me as I
> was at Centrium/Wapme but unfortunately I didn't merged it and don't
> have modifications anymore but it was really simple to fix. I will try
> to provide patch this/next week.
That would be great! Once this issue is resolved, Kannel will
effectively be working 'perfectly' for us :)
> as for the fact that MO messages are not retransmitted in smsbox: did
> you enable retry in smsbox?
As per the config I attached to my original email, http-request-retry
was set to 0, so no - the smsbox wasn't set to retry.
However, when I re-ran the test with http-request-retry = 10, I didn't
see any difference in behaviour - the log messages were the same
(indicating that http requests failed because of too many open files),
and I didn't see any indication that a retry was being attempted. The
Kannel docs seem to suggest that setting that parameter to a non-zero
value is all that's required to enable retransmits - am I missing
> Am 03.08.2006, 09:25 Uhr, schrieb Giulio Harding
> <giulio.harding at mnetcorporation.com>:
>> Hillel wrote:
>>> Are you using as a OpenSMPP SMSC simulator the
>>> or as another version?
>>> Please email back the version you are using, so others can confirm your
>> Sorry, it turns out the version of OpenSMPP we're using has been
>> heavily modified from the original - however, I have been able to
>> reproduce the problem using the latest version of SMPPSim, with the
>> following configuration options (modified only slightly from the stock
>> However, SMPPSim isn't as fast as OpenSMPP, so I had to run 4
>> instances on separate servers (with additional SMSC configurations in
>> Kannel accordingly) to reach an MO injection rate of ~600 MOs/sec (no
>> MTs), in order to trigger the problem.
>> At rates of ~450 MOs/sec, with no MTs, or ~350 MOs/sec + ~320 MTs/sec,
>> the problem did not surface.
>> Regardless of the SMSC simulator being used, MO injection rates of
>> around 600 MOs/sec (on the hardware I described before) triggers the
>> problem. Has anyone been able to reproduce this yet, or does anyone
>> have an idea why this might happen?
Level 13, 99 Gawler Place
Adelaide SA 5000, Australia
Tel: +61 8 8210 2041
Fax: +61 8 8211 9620
Mobile: 0432 876 733
MSN: giulio.harding at mnetcorporation.com
More information about the devel