Message store (Was: EMI: Serious Problem PANIC: Too many concurrent allocations)

Speaking of store files - After really looking into the store logic, it seems my notion of how store worked was all wrong : the elimination of messages that received acks/nacks from storage is done only on store_load, so it's quite possible that a long running Kannel will develop mighty store files which can bring any machine to its proverbial knees. IMO, it's not the right thing to do : message-ack matching should be done on-line, thus preventing issues of too big store files.

What do you people think ?

--
Oded Arbel
m-Wise Mobile Solutions

[email protected]
Mobile: +972-67-340014
Tel: +972-9-9581711 (ext: 116)

::..
Politicians should read science fiction, not westerns and detective stories.
	-- Arthur C Clarke


> -----Original Message-----
> From: Stipe Tolj [mailto:[email protected]]
> Sent: Wednesday, June 12, 2002 12:36 PM
> To: Bruno David Rodrigues
> Cc: [email 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 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 implement something like a HTTP status page for
> printing the contents of the store file to an HTTP client. This way we
> may "look into" the store file without the need to process it somehow
> via the command line.
> 
> Stipe
> 
> [email protected]
> -------------------------------------------------------------------
> Wapme Systems AG
> 
> Vogelsanger Weg 80
> 40470 Düsseldorf
> 
> Tel: +49-211-74845-0
> Fax: +49-211-74845-299
> 
> E-Mail: [email protected]
> Internet: http://www.wapme-systems.de
> -------------------------------------------------------------------
> wapme.net - wherever you are
> 
>