The server can't recover from a database failure

Hello,

This is a known issue, however it is considered minor, as the reliability of the connection to the database is a must in a production environment. I'm sure a cluster with hundreds of servers and thousands of user would have a database connection that is available 100% of the time during business hours. So in most cases, being aware of this limitation is sufficient to properly plan maintenance operations on a production environment (e.g. you should not perform database restarts during business hours, which is simply common sense)

In any case, patches are welcome to improve this, and there's one from the community considered for inclusion at this very moment. I'll link the relevant branch to this bug.

I hope you understand,

Thanks!

This issue should be fixed as of revision 4839 in the 7.0 server branch [1].

Thanks for your patience and thanks to everyone who contributed on getting it solved, especially Florent X. :-)

[1] revision-id: <email address hidden>

A typo remained in the patch that was merged, sorry about that. This is fixed after revision 4841 rev-id: <email address hidden>

@odony Thank you for your updates on this. It's much appreciated!

I replied on the initial MP why I believe the patch committed in haste in the 7.0 branch is not optimal

https://code.launchpad.net/~florent.x/openobject-server/trunk-bug-905257-fix-reconnect/+merge/132149/comments/322977

An update to this fix was merged at revision 4843[1], improving the performance of the fix as a follow-up to Florent's feedback. Sorry for the spam and for the confusion.

[1] revision-id: <email address hidden>

Another minor update to this fix was applied at revision 4849 rev-id: <email address hidden>, to remove a small side-effect spotted by Florent. It should not make any difference in most cases, just mentioning it for those tracking the bug in other branches.