Re: DLR insertiong/searching timing

Mohammed Saleem <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
I don't expect too uch MOs, so this should be OK, but I have some questions:

Which thread exactly sleeps? is it the same read/write thread on the SMPP
link socket? ( I have a bind_tranciever link without receiver-port ), if so
this may affect also the MT sending, or will kannel spawns a new thread for
each received DLR?

Thanks


Best Regards,
Mohammed M I Sleem
http://www.abusleem.net

http://www.freakle.com - The Search Freak

http://www.colorle.com - color your Google search



On Mon, Nov 22, 2010 at 4:02 PM, Alejandro Guerrieri
<[email protected]>wrote:

> If the problem it's your aggregator returning DLR's before the message is
> ACK'ed, a FIFO won't help you.
>
> It's actually the aggregator's fault. I've created a patch that can help
> solve the issue:
>
> http://www.blogalex.com/archives/132
>
> NOTE: Since the thread sleeps while retrying the DLR's this has a
> performance penalty, so if you expect a high volume of MO traffic, I
> recommend you to NOT use it.
>
> If you only expect a few messages per second at most, you should be OK.
>
> Regards,
> --
> Alejandro Guerrieri
> [email protected]
>
>
>
> On 22/11/2010, at 14:33, Mohammed Saleem wrote:
>
>
> Dear Kannelers
>
>
> I have an issue with kannel finding DLRs, when a DLR is received (most
> probably with status=2 (FAILED) ) and kannel tries to find it in the DLR
> table (assuming MySQL DLR storage), then kannel doesn't find it because it
> has not been inserted yet !! looks there are 2 separated threads for
> insertion/finding and deleting DLRs in kannel and sometimes the  find/delete
> thread works sooner than the other one !! We need to have something like a
> FIFO Queue for DLR operations.
>
>
> Is there any fix for this? please advise
>
>
>
> Best Regards,
> Mohammed M I Sleem
> http://www.abusleem.net
>
> http://www.freakle.com - The Search Freak
>
> http://www.colorle.com - color your Google search
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.