c2c-oerpscenario team mailing list archive

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

@Kyle: You are right, this is an issue and there is no reason to prevent
new connections to the server while the scheduler is running. I would
expect some performance impact, but nothing else. Do you have a recipe
to reproduce this easily starting from a new database? Also you did not
mention if you are using the Web or GTK client or if that makes a
difference.

@Raphael: If you have more data suggesting how to track the original cause of this issue, or how to reproduce it consistently, please do not hesitate to share them. 
Are you saying that having the mrp scheduler process will cause the calls to login() via xml-rpc to have to wait? If this does not affect existing sessions, it suggests that it's not a general lock, but rather something specific to the login() call?

Thank you both!

** Project changed: openobject-addons => openobject-server

** Changed in: openobject-server
       Status: Triaged => Incomplete

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

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/713216

Title:
  MRP Locks down server

Status in OpenERP Server:
  Incomplete

Bug description:
  When using the Manufacturing scheduler in a medium sized environment
  the scheduler will lock down the server in a way where not a single
  user may connect to the server. The login window shows up but when you
  type your password and click login it goes to a white screen and
  nothing happens, because the manufacturing scheduler is preventing the
  server from letting anyone log in. If you were already logged in then
  you can use the program. Quite frustrating. Sure the manufacturing
  scheduler is supposed to run at night, but that is still a bug.