[MapProxy] client_timeout

[Oliver Tonnhofer]

On 30.11.2010, at 11:29, Sandor Csaba wrote:
> My problem is that I have a quite slow wms (mapserver cgi) and mapproxy doesn't wait for it until it finishes, but throws a timeout and tries again which gradually kills the server by starting lengthy mapserv processes again and again. This gets logged into the proxy.log:
> 
> 2010-11-29 18:22:59,896 - INFO - 16764:mapproxy.client.http.http:_log - localhost:81 - - [29/Nov/2010:18:22:58 ] "GET /cgi-bin/mapserv?map=/home/mapadmin/public_html/mapfiles/zoom3-16_hun_beta.map&&layers=FIRST&width=1043&version=1.1.1&bbox=1784156.0,5722664.0,2422558.06024,6221085.0&service=WMS&format=image%2Fpng&styles=&srs=EPSG%3A900913&request=GetMap&height=815 HTTP/1.1" 500 0 "-" ""
> 2010-11-29 18:23:02,565 - ERROR - 16764:mapproxy.service.tile:render - No response from URL (http://localhost:81/cgi-bin/ma...): timed out
> 
> If I copy the request url and paste it into a browser, de tile appears ok, after some minutes of waiting, so I suspect its not an apache timeout.
> 
> I found the client_timeout config option, but the server doesn't seem to take it into account.

Looks like a bug in 0.9.0. The default socket timeout is set before the actual configuration is read. I already changed that part and it will be fixed in 0.9.1. Until then you need to change the defaults manually in mapproxy/config/defaults.py (somewhere in lib/python-2.6/site-packages/).


Regards,
Oliver

-- 
Oliver Tonnhofer <olt at omniscale.de>
Omniscale - Dominik Helle, Oliver Tonnhofer GbR
Nadorster Str. 60, 26123 Oldenburg
Tel: +49(0)441/9392774-2 (Fax: 9)