On Wed, 2002-06-05 at 09:39, Aarno Syvänen wrote:
Paul Keogh kirjoittaa tiistaina, 4. kesäkuuta 2002, kello 14:51:
Yes, but when this is triggered bb_smscconn_receive () logs the event
and
returns -1. All the SMSC drivers except HTTP ignore the return code from
bb_smscconn_receive ().
; [EMAIL PROTECTED]
Subject: Re: EMI: Serious Problem PANIC: Too many concurrent allocations
On Wed, 2002-06-05 at 09:39, Aarno Syvänen wrote:
Paul Keogh kirjoittaa tiistaina, 4. kesäkuuta 2002, kello 14:51:
Yes, but when this is triggered bb_smscconn_receive () logs the
event
Bruno David Rodrigues kirjoittaa keskiviikkona, 12. kesäkuuta 2002,
kello 12:22:
Yes, it indeed seems that this code can use some rewriting :( Does
Paul's suggestion
met your big file needs (let us plan better this time).
Aarno
Paul Keogh kirjoittaa tiistaina, 4. kesäkuuta 2002, kello
On Wed, 2002-06-12 at 10:40, Warren Liu wrote:
There may be a possibility on the lack of ram on your machine maybe? On
our production machine, there are times during high traffic hours where
apache plus kannel was eating up almost everything in terms of ram and
cpu. Pushing close to the kind
Bruno David Rodrigues wrote:
I recall that smsbox*.log have each and every message but
bearerbox_*.log lost almost 25%.
but those messages that have been logged in smsbox.log, but *not* in
bearerbox.log have to be queued in the store file, right?!
Can you verify this?
BTW, I'd like to
PROTECTED]; 'Aarno Syv?en'; 'Paul Keogh';
[EMAIL PROTECTED]
Subject: Re: EMI: Serious Problem PANIC: Too many concurrent
allocations
Bruno David Rodrigues wrote:
I recall that smsbox*.log have each and every message but
bearerbox_*.log lost almost 25%.
but those messages that have
On Wed, 2002-06-12 at 11:36, Stipe Tolj wrote:
Bruno David Rodrigues wrote:
I recall that smsbox*.log have each and every message but
bearerbox_*.log lost almost 25%.
but those messages that have been logged in smsbox.log, but *not* in
bearerbox.log have to be queued in the store
Bruno David Rodrigues wrote:
On Wed, 2002-06-12 at 11:36, Stipe Tolj wrote:
Bruno David Rodrigues wrote:
I recall that smsbox*.log have each and every message but
bearerbox_*.log lost almost 25%.
but those messages that have been logged in smsbox.log, but *not* in
Paul Keogh kirjoittaa tiistaina, 4. kesäkuuta 2002, kello 14:51:
Yes, but when this is triggered bb_smscconn_receive () logs the event
and
returns -1. All the SMSC drivers except HTTP ignore the return code from
bb_smscconn_receive (). Therefore, the message is silently dropped from
the
Kannel currently has configuration variable maximum-queue-length. See
user-
guide for details.
Yes, but when this is triggered bb_smscconn_receive () logs the event and
returns -1. All the SMSC drivers except HTTP ignore the return code from
bb_smscconn_receive (). Therefore, the message
On Sat, 1 Jun 2002, Jari Juslin wrote:
So, panic to Too many concurrent allocations can happen if a) Kannel
just has so high load, that is needs huge amounts of memory or b) if
Kannel leaks too much memory. Am I right?
Yes. The reason a) is encountered when incoming traffic is faster than
Kalle Marjola kirjoittaa maanantaina, 3. kesäkuuta 2002, kello 10:37:On
Sat, 1 Jun 2002, Jari Juslin wrote:
So, panic to Too many concurrent allocations can happen if a) Kannel
just has so high load, that is needs huge amounts of memory or b) if
Kannel leaks too much memory. Am I right?
Jari Juslin wrote:
Jari Juslin wrote:
Further question: In general situation, does this really correct
problems or just hide them?
Ok, I was a bit hasty once again. By reading the mailing list archive
and code I came to this asumption: if I want to run Kannel under heavy
load, I
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
Jari Juslin wrote:
Further question: In general situation, does this really correct
problems or just hide them?
Ok, I was a bit hasty once again. By reading the mailing list archive
and code I came to this asumption: if I want to run Kannel under heavy
load, I need to increase
Kalle Marjola wrote:
Hm, this question needs to be a s a first one in FAQ, it is so often
asked.. (in fact I could not find it from FAQ section at all..)
definitly +1 ;)
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
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
Hi,
I have this problem
I'm trying to send out SMS Broadcast and after a while kannel just die because of
PANIC: Too many concurrent allocations
Is that any way i can increase the concurrent allocations process?
Base on your experience, how many SMS can kannel process per second?
I'm using
18 matches
Mail list logo
