Fix some message persistence problems after first deploy (!608) · Merge requests · BC / public / flexisip · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Anthony Gauchy requested to merge fix/message_persistence into master Dec 02, 2021

late fork timer was deleted when message is in database --> now the proxy object create its own timer while message is in database.
on server startup all messages were restored in memory --> now only useful data to create proxy objects are restored.
minor code and comment improvement.