Kamailio (OpenSER) SIP server / Bugs / #587 Presence DB save fails after one failure

#587 Presence DB save fails after one failure

Milestone: ver 1.5.x

Status: open

Owner: nobody

Labels: modules (357)

Priority: 5

Updated: 2009-07-24

Created: 2009-07-24

Creator: Alex Hermann

Private: No

After one record has failed to insert/update into the database, remaining records aren't tried.

The attached patch tries to insert/update the remaining records in the hashtable after a failure.

This patch surfaced bug #2824350 which led to a lot of failures due to duplicate keys.

Discussion

Alex Hermann - 2009-07-24

Continue updating DB after failure

fix-subscribe-continue-after-db-failure.diff

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

sathiyapriyan m - 2009-10-05

How to Repeat or Check the Error? Kindly explain the situation. I have tried in may ways it works fine in the version 1.5.2.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Alex Hermann - 2009-11-10

just let the DB update fail in some way. I got a duplicate key error somehow.

The patch makes sure the remaining entries in the hash table are committed to the DB even after one record failed.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2009-11-10

You can commit the patch - I was waiting for you to test if svn access works ok.

Daniel

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.