> If you update the underlying data frequently in the work that you do and
> can't wait on a bugfix, I would try to determine what else forces an update,
> such as clearing Geoserver's cache for the layer, etc ( potentially relevant:
> http://gis.stackexchange.com/questions/77240/ ) .
Sabine –
Hm. I may be wrong, but this sounds like a bug. You might consider filing a
report.
If you update the underlying data frequently in the work that you do and can't
wait on a bugfix, I would try to determine what else forces an update, such as
clearing Geoserver's cache for the layer,
Sabine, it seems you have the request logging filter enabled and logging
fully bodies (see web.xml)... disable it if you want to make large uploads,
or provide a patch to set a limit to how much gets logged (the logging
filter is considered a debugging tool, not to be used
for production, that's
Hello Sabine,
The reference values for the parameters applied for optimizing JVM in
tomcat (based on some research) are below but obviously this is not a rule
of thumb:
HEAP="-Xms2048m -Xmx2048m"
NEW="-XX:NewSize=128m -XX:MaxNewSize=128m"
RMIGC="-Dsun.rmi.dgc.client.gcInterval=60 -
Dear List,
I am using Geoserver 2.7.5 and I am using REST Api for creating datastores and
layers.
Now I have the problem that Geoserver throws a java.lang.OutOfMemoryError:
Exception in thread "ajp-bio-9018-exec-5" java.lang.OutOfMemoryError: Java heap
space
at
Hi Patrick,
I also tried viewing the data via an OpenLayers web application (not only
Geoservers prewiew) and the data is still clipped to the old bounding box.
Sabine
>
> Have you tried viewing the data in QGIS or OpenLayers before and after
> changing the bounding box? Are data being
Hi Anton,
Please, keep the conversation on the mailing list so others can help you
or benefit from our conversation.
I don't use gsconfig, so I'm not able to help you with it. However, once
you set up your PostGIS JNDI datastore, it's just another datastore and
I wildly guess that gsconfig
