If you're using CherryPy 3.1, you have several workarounds:
- either add SetEnv proxy-nokeepalive 1 in your Apache virtualhosts
- better solution: add this in your web client config: server.socket_timeout = 60 (60 is arbitrary)
Changing ProxyTimeout did not change anything for me.
But since the real bug is in cherrypy, the best solution is to upgrade at least to cherrypy 3.2.0, or 3.2.2.
For the OpenERP web client 6.0 branch maintainers, the best thing is to :
- change the doc in http://doc.openerp.com/v6.0/install/linux/web/index.html to tell CherryPy >= 3.2.0. I woul also require to use at least python>=2.6 (but I've checked the minimal python version required by cherrypy)
- change the requirements in the web client's setup.py to : "CherryPy >= 3.2.0" and not "CherryPy == 3.1.2". BTW it's a bad idea to pin egg versions in the setup.py because you prevent people from upgrading. Versions should rather be chosen either manually, or in a pip requirements file, or better in a buildout [versions] section.
OK after trying everything for hours, here is my conclusion. Could you please check if I'm right?
First here are some relevant links: www.openerp. com/forum/ topic12945. html groups. google. com/group/ cherrypy- users/browse_ thread/ thread/ e751976da1d0139 0
http://
http://
The real issue comes from this : ======= ======= ==== /bitbucket. org/cherrypy/ cherrypy/ issue/853/ consistent- time-out- of-the- wsgi-server
=======
https:/
If you're using CherryPy 3.1, you have several workarounds: socket_ timeout = 60 (60 is arbitrary)
- either add SetEnv proxy-nokeepalive 1 in your Apache virtualhosts
- better solution: add this in your web client config: server.
Changing ProxyTimeout did not change anything for me.
But since the real bug is in cherrypy, the best solution is to upgrade at least to cherrypy 3.2.0, or 3.2.2.
For the OpenERP web client 6.0 branch maintainers, the best thing is to : doc.openerp. com/v6. 0/install/ linux/web/ index.html to tell CherryPy >= 3.2.0. I woul also require to use at least python>=2.6 (but I've checked the minimal python version required by cherrypy)
- change the doc in http://
- change the requirements in the web client's setup.py to : "CherryPy >= 3.2.0" and not "CherryPy == 3.1.2". BTW it's a bad idea to pin egg versions in the setup.py because you prevent people from upgrading. Versions should rather be chosen either manually, or in a pip requirements file, or better in a buildout [versions] section.
For the buildout part, I'll update the recipe to take this into account. http:// pypi.python. org/pypi/ anybox. recipe. openerp