openerp-india team mailing list archive

["Kyle Waid - http://www.gcotech.com" <992525@xxxxxxxxxxxxxxxxxx>]

Hello, I receive the error in many different ways. One way I was able to
reproduce it,

3 different users (unique logins) try to confirm production of a bill of
materials. Granted it was the same one, 2 users received the error while
the third succeeded.

Another way I receive the error frequently is installing new modules, I
have been able to reproduce the problem on 10 systems with current code
easily, but other openerp core developers say they cant reproduce it.
The problem seems worse when trying to install module from the kanban
view. The issue besides the error message is not being able to run the
configuration wizards.

Another way I was able to reproduce it is by trying to import orders
using magento connection. I see the error a lot in this way. Olivier you
explain a possible relief, I will see about having this developed in a
module or something

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

Title:
  TransactionRollbackError due to concurrent update could be better
  handled

Status in OpenERP Server:
  Confirmed

Bug description:
  While using openerp, psycopg2 raises TransactionRollbackError quite
  often even on small database.

  This does not seem to be easily reproduceable as it seems to be a
  conflict between two thread accessing the same table. Nevertheless, I
  provided a quick video reproducing this while installing "base_crypt"
  on my computer.

  This occurs mostly at module installation. And can completely mess up
  the module installation by giving empty wizard windows of instance.

  I guess it could also occurs in other situations (in multi-user
  context), where the bug would be quite difficult to reproduce and with
  unforeseeable consequences ;)

  I've spotted an other bug that is due to this it seems:
  https://bugs.launchpad.net/bugs/956715

  In my case (single user), it seem to hit more often on fast computers.
  To make a probable better guess, it seems to hurt more often whenever
  using a local connection between the browser and the server. It could
  be about the web module trying to update the res_users session info
  and may collide with normal operation.

  On my computer, from a new database, installing the 'base_crypt' will trigger the exception.
  When using a distant connection, the bug won't show up.

  Please check the video I've posted with the bug report if you want to
  have more detail on the procedure I used. Sorry for the bad sound
  recording. Note that the video will show you the bug occuring on my
  computer and NOT occuring on a distant computer.

  I'm providing a merge proposal along with this patch which solves the
  issue for me, but need a patient review.

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