openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #12314
[Bug 992525] Re: TransactionRollbackError due to concurrent update could be better handled
Hello,
I am having serious problems with this type of error on 6 different
systems. Most of the time it occurs when installing a new module, but
other times it happens when running scheduled processes, or just running
concurrent processes in general. I reported a similar bug before, but it
was marked as invalid. I find this problem exists throughout the program
and it is a serious problem in this software release that has existed
for a few months but has not been fixed. I was going to migrate a
customer to 6.1, but now I strongly reconsider due to this issue. I see
stability issues within the software that makes it unusable in a
production environment with many users. This problem as you know does
not exist in previous releases.
--
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
References