openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <905257@xxxxxxxxxxxxxxxxxx>]

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!

** Changed in: openobject-server
   Importance: Undecided => Wishlist

** Changed in: openobject-server
       Status: New => Confirmed

** Changed in: openobject-server
     Assignee: (unassigned) => OpenERP's Framework R&D (openerp-dev-framework)

** Branch linked: lp:~florent.x/openobject-server/trunk-fix-reconnect

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/905257

Title:
  The server can't recover from a database failure

Status in OpenERP Server:
  Confirmed

Bug description:
  In version 6.0. I'm using 6.0.1.
  When the database stops the server can't reconnect to the database, and in this situation two bad things happens:
  i) The web client, don't send the correct message to the user. The feedback a user receives is that the username/password is incorrect, this leads to frustration and confusion of users. The correct behavior would be to report for example “server or database not ready”.
  ii) After that all openerp servers must be restarted, shutting down all user sessions, imagine a cluster with hundreds of server, thousands of users.
  To reproduce just stop, and try to use the web client, start database again,  and try to use the web client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/905257/+subscriptions