c2c-oerpscenario team mailing list archive

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

No, malformed PO (if there were any) cannot cause this behavior, because they are not loaded or parsed in separate threads.
You're looking for a module that spawns background threads that never stop running, possibly waiting for requests to service.

As you seem to have databases that do not exhibit this behavior, you
could compare the list of installed modules between them.

One last thing you can try is to signal the OpenERP server process with a "QUIT" signal, either by hitting CTRL+4 on the terminal where the server is currently running (as a *foreground* process), or by using "sudo kill -3 <PID>" where <PID> is the process ID of the openerp-server process. This will cause the server to write in the log a dump of all the threads that are currently running. This will give us clues as to what module they come from (disclaimer: we're getting very technical here ;-)).
You would need to first remove the os._exit() line of your patch, to give you some time to send the signal before stopping the process the hard way.

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

-- 
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/824783

Title:
  v6 stop_after_init does not exit

Status in OpenERP Server:
  Incomplete

Bug description:
  please see last comment on
  https://bugs.launchpad.net/openobject-server/5.0/+bug/574874
  can not change the status of the bug  there

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