! zip attachement refused! trying with DropBox link.
···
2015-08-11 14:17 GMT+02:00 Andrea Aime <andrea.aime@anonymised.com>:
On Tue, Aug 11, 2015 at 12:57 PM, Scotti Roberto <roberto.scotti@anonymised.com> wrote:
Hello
Many thanks for the suggestion.I downloaded the log and tried to examine it.
I do read the word “ERROR” in connection with the conclusion of the WFS request for the shapefile “sottocategorie_ag”.
I do not see the beginning of the request.
I suppose the last line documents the initial request.
The ERROR says:
“2015-08-11 05:30:32,567 ERROR [geoserver.ows] -
java.lang.OutOfMemoryError: Java heap space”Can this be due to “invalid geometries”?
The Geoserver is running on a PVS (Digital Ocean Droplet) with 512 MB
Ah, this might be the cause. How did you install/deploy GeoServer?
It might be running with just 64MB of memory on such a small machine
(Java server side ergononomics not kicking in, and as result, the JVM
running as if it was working on an applet).
We should ensure that it runs with at least 256MB in that environment, but to
do so, we need to know how you deployed it.
We normally recommend to run GeoServer with 2GB of heap, on a machine that has at least 4GB
of memory, it’s possible to run it with less of course, but it will severely limit the amount of
concurrent requests one can handle.
Your WFS download can be going OOM because of many reasons, large geometries
being one, concurrent requests being another (and if you’re running GeoServer with
just 64m of memory, well, we should be thankful it started at all)
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.
memory. Is this cause of the error? Is the software not able to forecast that heap will need more space than what is available in order to manage the situation? Such a problem can occur with any memory dimension or is there a minimum memory requirement in order to avoid it?