openerp-community-reviewer team mailing list archive

[Daniel Reis <dgreis@xxxxxxx>]

On load stress, I was able to produce SERIALIZATION_FAILURE errors, but not sure if this is rather an oe-server performance limitaion instead of a problem specific of the module.
(I opened several browser windows and loaded in all of them a page that takes several seconds).


2014-05-02 09:50:27,580 43126 ERROR qld-main openerp.sql_db: bad query: insert into "server_monitor_process" (id,"info","cpu_time","uid","thread","pid","memory","model","method","name",create_uid,create_date,write_uid,write_date) values (15313,'rpc call',117.947371,922,'Thread-332',43126,1899307008.0,NULL,'read','2014-05-02 09:50:27',1,(now() at time zone 'UTC'),1,(now() at time zone 'UTC'))
Traceback (most recent call last):
  File "/opt/openerp/src/ocb-7.0-latest/server/openerp/sql_db.py", line 226, in execute
    res = self._obj.execute(query, params)
TransactionRollbackError: could not serialize access due to concurrent update
CONTEXT:  SQL statement "SELECT 1 FROM ONLY "public"."res_users" x WHERE "id" OPERATOR(pg_catalog.=) $1 FOR SHARE OF x"

2014-05-02 09:50:27,596 43126 INFO qld-main openerp.osv.osv: SERIALIZATION_FAILURE, retry 1/5 in 0.9637 sec...

-- 
https://code.launchpad.net/~camptocamp/server-env-tools/7.0-monitoring/+merge/215138
Your team Server Environment And Tools Core Editors is subscribed to branch lp:server-env-tools.