Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FIX] website: prevent SQL deadlock with website.visitor
Since it's first implementation at [1], a new cursor is created to then build a new environment after the website's `authenticate` overide with the new `uid` of the logged in user. Since the new visitor SQL upsert refactoring done at [2], it seems to be introducing a SQL deadlock sometimes. It has been detected on odoo.com while monitoring the logs. Despite being quite rare, it still happens too often due to our heavy trafic. Step to reproduce (among others): - Install website_livechat - Login as admin on 127.0.0.1 - On 127.0.0.2, load the website - Open the livechat - Type something in the discussion - Directly try to login as admin - It will load for a certain time then crash on a 502 timeout due to the SQL deadlock - You may need to repeat the process to actually face the bug [1]: odoo@6bec0e4 [2]: odoo@d348bed closes odoo#109746 Signed-off-by: Olivier Dony (odo) <[email protected]>
- Loading branch information