JSONDB fails to connect to sqlite3 #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP
Here is what is happening. We are connect with multiple ZMQ sockets to NodeManager with each instance of
openbts.components.SIPAuthServe()and it seems that they are competing for the connection to the sqlitedb. This was coming up in phone_tests on clientThis adds a 10x retry spaced 0.1 seconds apart in the attempt that the connection fails. I think this is what we were doing pre-openbts 5.0
I am tempted to move the
connect()to https://github.com/endaga/subscriberRegistry/blob/master/apps/sipauthserve.cpp#L64 so that we have one sqlite3 connection per instance ofsipauthservebut need to better understand the repercussions of that