← Back to team overview

openerp-india team mailing list archive

[Bug 905257] Re: The server can't recover from a database failure

 

** Also affects: ocb-server
   Importance: Undecided
       Status: New

** Also affects: ocb-server/7.0
   Importance: Undecided
       Status: New

** Changed in: ocb-server/7.0
       Status: New => Fix Committed

** Changed in: ocb-server/7.0
     Assignee: (unassigned) => Stefan Rijnhart (Therp) (stefan-therp)

** Changed in: ocb-server/7.0
   Importance: Undecided => Medium

** Also affects: therp-backports
   Importance: Undecided
       Status: New

** Also affects: therp-backports/server-6.1
   Importance: Undecided
       Status: New

** Changed in: therp-backports/server-6.1
       Status: New => Fix Committed

** Changed in: therp-backports
       Status: New => Fix Committed

** Changed in: therp-backports/server-6.1
     Assignee: (unassigned) => Stefan Rijnhart (Therp) (stefan-therp)

** Changed in: therp-backports
     Assignee: (unassigned) => Stefan Rijnhart (Therp) (stefan-therp)

-- 
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 Community Backports (Server):
  Fix Committed
Status in OpenERP Community Backports (Server) 7.0 series:
  Fix Committed
Status in OpenERP Server:
  Confirmed
Status in Therp Backports:
  Fix Committed
Status in Therp Backports server-6.1 series:
  Fix Committed

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/ocb-server/+bug/905257/+subscriptions