[Zoo-discuss] BufferPy problem

[Gérald Fenoy]

Dear Farkas,
merry Christmas, I think you should try running to run the same request from the command line directly by running cmd, then change directory to the ZOO-Kernel path and run the following command :

.\zoo_loader.cgi "<YOUR_REQUEST>" 2> log

Note that you may also add some debugging messages at each steps (for each geometry treated by the service) in the python script to get more information. Did you take a look at the cache file ? Is it correct / valid ? In other case you may try to remove the file then try again the same query. Does the apache user get the right to access the cache file ?

At the first step I thought it was only a timeout issue following log messages you provided, sorry I made a mistake here. The issue seems to come from another place. But I really think better to first check the cache file.

Hope to hear back from you and to be able to support you next time.

Best regards

Gérald Fenoy
gerald.fenoy at geolabs.fr

Le 25 déc. 2012 à 22:34, Farkas H <farkas.dus at gmail.com> a écrit :

> Hi Gérald,
> 
> first I want to wish you a merry Christmas.
> Thank you for your response.
> 
> For this test I used zoo-kernel from 2012-12-18 without any further
> developments.
> The response time on the client side for calculating seven buffers for
> the topp:tasmania_water_bodies layer from http://demo.opengeo.org
> takes about three seconds via HSDPA without caching. There is no
> timeout variable set in the httpd.conf file during OSGeo4W
> installation. The standard apache timeout is five minutes. The
> response time for calculating 49 buffers for the topp:states layer
> from the same server should take less than five minutes. What do you
> mean?
> 
> Even after I've set the timeout variable to 3600 [seconds] (60
> minutes) I got no response.
> 
> When the tiemout was reached (after 5 or 60 minutes) I got the
> following error message in the OSGeo4W apache log file:
> "Script timed out before returning headers: zoo_loader.cgi".
> I think the problem is not the server timeout.
> 
> Thank you for your occasional support.
> 
> Regards,
> Farkas
> 
> 
> On Dec 23, 2012 12:01 PM, "Gérald Fenoy" <gerald.fenoy at geolabs.fr> wrote:
>> 
>> Hi Farkas,
>> I guess that the issue doesn't come from the ZOO-Kernel itself but from the configuration of your web server which return a timeout.
>> 
>> It should simply mean that the web server consider that the ZOO-Kernel took too much time to handle the request. Which may be the case when you are using huge dataset. You should take a look into your web server configuration to fix this issue.
>> 
>> Hope you can confirm that the issue can be solved by setting longer timeout limit in your webserver configuration.
>> Best regards,
>> 
>> Gérald Fenoy
>> gerald.fenoy at geolabs.fr
>> 
>> Le 20 déc. 2012 à 21:52, Farkas H <farkas.dus at gmail.com> a écrit :
>> 
>>> Hi everyone,
>>> 
>>> this http-Post buffer request [1] (BufferPy, buffers around features
>>> from layer topp:tasmania_water_bodies, 7 features) works.
>>> If I change the layer to topp:states (49 features) the request doesn't
>>> work [2]. You find the error message here [3].
>>> If I buffer just one feature from the states layer the request works
>>> [4]. Every single feature works.
>>> 
>>> I've noticed this behavior in other layers. One feature works the
>>> whole layer doesn't work.
>>> It looks like that the request from a certain number of objects does
>>> not work anymore.
>>> 
>>> What's wrong?
>>> 
>>> I appreciate any advice.
>>> 
>>> Regards,
>>> Farkas
>>> 
>>> [1]
>>> <wps:Execute service="WPS" version="1.0.0"
>>> xmlns:wps="http://www.opengis.net/wps/1.0.0"
>>> xmlns:ows="http://www.opengis.net/ows/1.1"
>>> xmlns:xlink="http://www.w3.org/1999/xlink"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xsi:schemaLocation="http://www.opengis.net/wps/1.0.0
>>> http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd">
>>> <ows:Identifier>BufferPy</ows:Identifier>
>>> <wps:DataInputs>
>>> <wps:Input>
>>> <ows:Identifier>InputPolygon</ows:Identifier>
>>> <ows:Title>water bodies</ows:Title>
>>> <wps:Reference xlink:href="http://demo.opengeo.org/geoserver/ows?Request=GetFeature&Service=WFS&Version=1.0.0&Typename=topp:tasmania_water_bodies"/>
>>> </wps:Input>
>>> <wps:Input>
>>> <ows:Identifier>BufferDistance</ows:Identifier>
>>> <ows:Title>Emergency area.</ows:Title>
>>> <wps:Data>
>>> <wps:LiteralData>0.01</wps:LiteralData>
>>> </wps:Data>
>>> </wps:Input>
>>> </wps:DataInputs>
>>> <wps:ResponseForm>
>>> <wps:ResponseDocument storeExecuteResponse="false">
>>> <wps:Output asReference="true">
>>> <ows:Identifier>Result</ows:Identifier>
>>> </wps:Output>
>>> </wps:ResponseDocument>
>>> </wps:ResponseForm>
>>> </wps:Execute>
>>> 
>>> [2]
>>> ...
>>> <wps:Reference xlink:href="http:...;Typename=topp:states"/>
>>> ...
>>> 
>>> [3]
>>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
>>> <html><head>
>>> <title>504 Gateway Time-out</title>
>>> </head><body>
>>> <h1>Gateway Time-out</h1>
>>> <p>The gateway did not receive a timely response
>>> from the upstream server or application.</p>
>>> </body></html>
>>> 
>>> [4]
>>> ...
>>> <wps:Reference xlink:href="http:...;Typename=topp:states&FeatureID=states.1"/>
>>> ...
>>> _______________________________________________
>>> Zoo-discuss mailing list
>>> Zoo-discuss at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss
>> 
> _______________________________________________
> Zoo-discuss mailing list
> Zoo-discuss at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss