On Sat, 2002-06-01 at 02:11, Jari Juslin wrote: > Kalle Marjola wrote: > > >On 24 May 2002, Abd Rahman Johari wrote: > > > > > >>I'm trying to send out SMS Broadcast and after a while kannel just die > >>because of PANIC: Too many concurrent allocations > >> > >> > > > >You need to compile Kannel with non-checking malloc, i.e. use native > >malloc. ./configure --with-defaults=speed or --with-malloc=native should > >help. > > > > > Further question: In general situation, does this really correct > problems or just hide them? I though that the checking malloc spots > errors and making error messages to go away by just not checking anymore > sounds quite hazard.. Or is it so, that this "Too many concurrent > allocations" checking failing does not always mean there is an error? I > have got the smsbox to panic this way when put under too heavy load and > bearerbox when restoring big enough store file (1000+ messages), and > these sound like this message would occur more often when Kannel is put > under high pressure (and possibly making much concurrent allocations for > some good reason?).
The concurrent allocations are relative to the checking malloc, that is limited (or configured somewhere in the code) to 1 or 2 MB. If you use native malloc, the limit should be the memory available. I've sent 200K (10k at once, with post-xml) messages and had the store.lock as bigger than 40MB, with 30k messages in queue. I don't recall now the exact values, but I were always expecting to see kannel crashing somewhere, but it worked out ok.
