THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#126 - 3.x dialog module: dialogs stay in database when in "shutdown only"
mode
User who did this - Timo Reimann (tr)
----------
Finally, I came to analyze the issue: The reason why it doesn't work is that on dialog
module startup, any database-related functionality during run-time is prohibited if the
database mode is SHUTDOWN. For that mode, however, there is no code to clear the database
after startup; the dialog-processing code in dlg_handlers.c relies on the assumption that
dialogs can be deleted from the database during run-time which is not possible in SHUTDOWN
mode. This is pretty much what Henning already discovered in the original mailing list
thread under
http://lists.kamailio.org/pipermail/users/2009-December/025811.html
The possible fixes are also there:
(1) Make database removal possible during run-time
(2) Clear the database either prior to serializing during shutdown or after de-serializing
during startup.
My personal preference goes towards (2) to have SHUTDOWN mode behave as expected: Access
the database only when needed to serialize/de-serialize dialogs without any run-time
requirements.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=126#comment2…
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.