Could not serialize access due to concurrent update

[Давид]

Hello,

Since its 6.0 started.

Please fabien(<email address hidden>) improve this.

Even just moving single canban card to other stage. it show below traceback.

Please fix it soon.

2012-12-01 15:31:03,048 2576 ERROR ? openerp.sql_db: bad query: update project_task set "sequence"=2,write_uid=1,write_date=(now() at time zone 'UTC') where id IN (3)
Traceback (most recent call last):
  File "/home/bonjour/stable/server/openerp/sql_db.py", line 212, in execute
    res = self._obj.execute(query, params)
TransactionRollbackError: could not serialize access due to concurrent update

2012-12-01 15:31:03,053 2576 INFO ? werkzeug: 127.0.0.1 - - [01/Dec/2012 15:31:03] "POST /web/dataset/save HTTP/1.1" 200 -
2012-12-01 15:31:03,080 2576 ERROR ? openerp.osv.osv: Uncaught exception
Traceback (most recent call last):
  File "/home/bonjour/stable/server/openerp/osv/osv.py", line 121, in wrapper
    return f(self, dbname, *args, **kwargs)
  File "/home/bonjour/stable/server/openerp/osv/osv.py", line 176, in execute
    res = self.execute_cr(cr, uid, obj, method, *args, **kw)
  File "/home/bonjour/stable/server/openerp/osv/osv.py", line 164, in execute_cr
    return getattr(object, method)(cr, uid, *args, **kw)
  File "/home/bonjour/stable/addons/project/project.py", line 1051, in write
    result = super(task,self).write(cr, uid, ids, vals, context=context)
  File "/home/bonjour/stable/server/openerp/osv/orm.py", line 3927, in write
    'where id IN %s', upd1 + [sub_ids])
  File "/home/bonjour/stable/server/openerp/sql_db.py", line 152, in wrapper
    return f(self, *args, **kwargs)
  File "/home/bonjour/stable/server/openerp/sql_db.py", line 212, in execute
    res = self._obj.execute(query, params)
TransactionRollbackError: could not serialize access due to concurrent update

2012-12-01 15:31:03,112 2576 ERROR ? openerp.netsvc: could not serialize access due to concurrent update

Thanks,
Kettor

[Serpent Consulting Services (serpent-consulting-services)]

Kettor,

We've also faced such issues, but most of the times it was due to calls of write() colliding with the scheduler calls.

Is your scheduler running on the same model (project.task)?

We still feel server can manage this.

Thanks.