Hello there,

I'm currently having issues with Kannel delivering MTs in LIFO (last in
first out) priority mode.

I'm using Kannel 1.4.4 and filesystem directory spool storage (Debian
jessie, ext4).

I'm submitting large amounts of messages (let's call them "batch A)" for
via cgi-bin/sendsms http endpoint; they all get ingested in the store.

One hour later, some messages are still in queue, and I'm submitting a
large amount of another message (let's call them "batch B"), the same way.

Both messages are sent without any priority defined.


What I'm observing, in such situations, is that delivery of messages from
batch A are interrupted when batch B starts, Kannel is now only delivering
messages from batch B.
Deliveries for batch A will only resume when batch B is finished.

I've been trying to understand if Kannel "officially" working in LIFO or
FIFO, but can't really get a proper understanding.

9 years ago, Nikos seemed to indicate the queue should work in FIFO
https://www.kannel.org/pipermail/users/2010-July/011951.html

But that's really not what I'm observing.
Also, I found someone suggesting a patch to make Kannel work in FIFO
instead of LIFO (that would confirm my supposition)
https://stackoverflow.com/questions/37461349/kannel-queue-type

But unfortunately this does not get a lot of attention, and I'm not very
comfortable changing the source code as I have no experience in C.


What do you guys think?
Can anyone confirm if Kannel is operating in LIFO and the behaviour I'm
observing is normal?
Would anyone have a recommendation to achieve a FIFO behaviour without
taking too many risks?


Thanks a lot,

--
Louis

Reply via email to