THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#449 - CRASH: Program terminated with signal 6, Aborted.
User who did this - Nuno Miguel Reis (nmreis)
----------
Hi Daniel.
I've just started working this Monday again, after a 2 week vacation period and in the meanwhile didn't have the opportunity to test this issue better.
Nevertheless since you felt confident with your patches ans closed the issue, i'll let you know if the bug pops up again, eventually, as suggested.
Thanks and keep up the good work.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=449#comment1609
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hello Folks,
I found the root cause of this issue.
In file ms_msg_list.c, issue is on line 290.
(https://github.com/sipwise/kamailio/blob/master/modules/msilo/ms_msg_list.c
)
Line 290: p0 = p0->next;
should be like this below :
p0 = ml->lsent;
The issue is p0->next becomes null in first iteration so it won't process
more than one element in 'while' loop. Hence this is the main cause of
slowness of message deletion.
I have tested modified code and it works fine now.
Develoerps,
Please review this change and advise accordingly.
Thanks
On Mon, Aug 25, 2014 at 11:35 PM, Bhupendra Singh <bsingh(a)bsingh.net> wrote:
> Hi Guys,
>
> Has anyone used/using offline message handling and storage in "silo" table?
> My issue is cleanup of stored message is taking very long time specially
> when many messages are left for target users.
> After further investigation I realized, only one message gets deleted in
> one pass and next in next pass ( after 30 second default timer).
> Is it intentional ? How can we make sure that all delivered messages get
> deleted right away for that user?
>
> Thanks
>
>
>