In facts, I has compiled GW without option "--enable-malloc", 'cause "native' is default option. Addition, how to compilea part of GW with "native" and other with "checked" option of malloc??? :)
DR
Andreas Fink <[EMAIL PROTECTED]>wrote:
On Mittwoch, September 4, 2002, at 06:42 Uhr, Rumsfeld
-Original Message-From: Rumsfeld Donald
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, September 04, 2002
6:42 AMTo: Oded ArbelCc:
[EMAIL PROTECTED]Subject: RE: "PANIC: Too many concurrent
allocations"
Hi all,
My GW was built with native mem-check (default op
Could
happen on an old version with some memory leaks which is running for quite a
while and was compiled with checking malloc. you can either upgrade to the
latest CVS or recompile it with native malloc to solve this issue. the later
solution will cause the error to go away, but will still
Hi all,
My GW was built with native mem-check (default option).
I think that this error was caused by allocation memory too much.
Is there some packetsthat allocated memory before, butwould not released after life-time ?
Is there any way to watch packets from the time it's allocated memory to the
ml wrote:
hi, Jörg
we met the problem too.
but if we compile kannel with native malloc mode , the following PANIC occur,
2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure!
2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument
thanks best regards
ml
This itself
yep i have seen this problem with 1.1.5
I have a simulator that the best i get is about 20 msgs per second
before getting the same errors ... this was with 4 different connections
sendinging a request to an application not just a nop
-Original Message-
From: [EMAIL PROTECTED]
we had experienced the same problems when batch messages are sent thro HTTP
interface to Kannel. This is probably due to outgoing message queue overflow
in bearerbox. Since the flow control is at SMSC -- bearerbox interface.
Messages from smsbox interface are pumped into bearerbox and kept in
