date:20160929

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

2016-09-29 Thread P O'Toole

> 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/ ) . (Obviously, you've found 
> that deleting/recreating the layer does the trick.) From there, you may just 
> automate this, and arrange to clone/delete/remake/empty the cache for the 
> layer using Geoserver's configuration REST API, and have this happen either 
> periodically or whenever you make edits from your database.

If it looks like it's a caching issue, you may also just set a really short 
cache-lifetime for the resources in question so you're not hitting stale data 
for long.

- Patrick


-Original Message-
From: P O'Toole 
Sent: Thursday, September 29, 2016 1:01 PM
To: Sabine Ohlendorf 
Cc: geoserver-users@lists.sourceforge.net
Subject: RE: Re: Problem changing bounding box of imagemosaic layer

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, etc ( potentially relevant: 
http://gis.stackexchange.com/questions/77240/ ) . (Obviously, you've found that 
deleting/recreating the layer does the trick.) From there, you may just 
automate this, and arrange to clone/delete/remake/empty the cache for the layer 
using Geoserver's configuration REST API, and have this happen either 
periodically or whenever you make edits from your database.

- Patrick

-Original Message-
From: Sabine Ohlendorf [mailto:sabine.ohlend...@gmx.de] 
Sent: Thursday, September 29, 2016 2:07 AM
To: P O'Toole 
Cc: geoserver-users@lists.sourceforge.net
Subject: Aw: Re: Problem changing bounding box of imagemosaic layer

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 clipped to the old bounding box 
> still or is it simply Geoserver's preview that's going stale when you chance 
> the bbox?
> 
> - Patrick O'Toole
> 
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

2016-09-29 Thread P O'Toole

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, etc ( potentially relevant: 
http://gis.stackexchange.com/questions/77240/ ) . (Obviously, you've found that 
deleting/recreating the layer does the trick.) From there, you may just 
automate this, and arrange to clone/delete/remake/empty the cache for the layer 
using Geoserver's configuration REST API, and have this happen either 
periodically or whenever you make edits from your database.

- Patrick

-Original Message-
From: Sabine Ohlendorf [mailto:sabine.ohlend...@gmx.de] 
Sent: Thursday, September 29, 2016 2:07 AM
To: P O'Toole 
Cc: geoserver-users@lists.sourceforge.net
Subject: Aw: Re: Problem changing bounding box of imagemosaic layer

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 clipped to the old bounding box 
> still or is it simply Geoserver's preview that's going stale when you chance 
> the bbox?
> 
> - Patrick O'Toole
> 
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] OutOfMemoryError: Java heap space

2016-09-29 Thread Andrea Aime

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 why it does not have a built-in limit, but one could
be added)

Cheers
Andrea


On Thu, Sep 29, 2016 at 10:17 AM, Sabine Ohlendorf 
wrote:

> 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 java.util.Arrays.copyOf(Arrays.java:2367)
> at java.lang.AbstractStringBuilder.expandCapacity(
> AbstractStringBuilder.java:130)
> at java.lang.AbstractStringBuilder.ensureCapacityInternal(
> AbstractStringBuilder.java:114)
> at java.lang.AbstractStringBuilder.append(
> AbstractStringBuilder.java:415)
> at java.lang.StringBuffer.append(StringBuffer.java:237)
> at org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.
> format(PatternParser.java:420)
> at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
> at org.apache.log4j.WriterAppender.subAppend(
> WriterAppender.java:301)
> at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
> at org.apache.log4j.AppenderSkeleton.doAppend(
> AppenderSkeleton.java:230)
> at org.apache.log4j.helpers.AppenderAttachableImpl.
> appendLoopOnAppenders(AppenderAttachableImpl.java:65)
> at org.apache.log4j.Category.callAppenders(Category.java:203)
> at org.apache.log4j.Category.forcedLog(Category.java:388)
> at org.apache.log4j.Category.info(Category.java:663)
> at org.geotools.util.logging.Log4JLogger.info(Log4JLogger.
> java:135)
> at org.geoserver.filters.LoggingFilter.doFilter(
> LoggingFilter.java:81)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:42)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.geoserver.filters.SessionDebugFilter.doFilter(
> SessionDebugFilter.java:48)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.geoserver.filters.FlushSafeFilter.doFilter(
> FlushSafeFilter.java:44)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(
> SetCharacterEncodingFilter.java:109)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.apache.catalina.core.StandardWrapperValve.invoke(
> StandardWrapperValve.java:220)
> at org.apache.catalina.core.StandardContextValve.invoke(
> StandardContextValve.java:122)
>
> First I thought that the image that I wanted to upload was too big, approx
> 260MB. But I could upload a much bigger image (700MB) without problems.
> I read a lot within the list but could not find a solution. As described
> in http://docs.geoserver.org/latest/en/user/production/
> troubleshooting.html I printed the heap status via jmap but to be honest
> I cannot read anything out of it:
>
> Attaching to process ID 2023, please wait...
> Debugger attached successfully.
> Server compiler detected.
> JVM version is 24.75-b04
>
> using thread-local object allocation.
> Parallel GC with 1 thread(s)
>
> Heap Configuration:
>MinHeapFreeRatio = 0
>MaxHeapFreeRatio = 100
>MaxHeapSize  = 3288334336 (3136.0MB)
>NewSize  = 1310720 (1.25MB)
>MaxNewSize   = 17592186044415 MB
>OldSize  = 5439488 (5.1875MB)
>NewRatio = 2
>SurvivorRatio= 8
>PermSize = 21757952 (20.75MB)
>MaxPermSize  = 268435456 (256.0MB)
>G1HeapRegionSize = 0 (0.0MB)
>
> Heap Usage:
> PS Young Generation
> Eden Space:
>capacity = 522190848 (498.0MB)
>used = 35361864 (33.72370147705078MB)
>free = 486828984 (464.2762985229492MB)
>6.77182760583349% used
> >From Space:
>

Re: [Geoserver-users] OutOfMemoryError: Java heap space

2016-09-29 Thread Alberto Callejas Delgado

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 -
Dsun.rmi.dgc.server.gcInterval=60"
PGC="-XX:+UseParallelGC"
PERM="-XX:PermSize=128m -XX:MaxPermSize=128m"
DEBUG="-verbose:gc -XX:+PrintTenuringDistribution"
DUMP="-XX:+HeapDumpOnOutOfMemoryError"
SERVER="-server"

Try to investigate a bit more about each parameter and try to find the best
solution for your needs.

I would say the parallel garbage collector (Parallel GC) with 1 thread
might be to low.

Best,

Alberto

On 29 September 2016 at 09:17, Sabine Ohlendorf 
wrote:

> 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 java.util.Arrays.copyOf(Arrays.java:2367)
> at java.lang.AbstractStringBuilder.expandCapacity(
> AbstractStringBuilder.java:130)
> at java.lang.AbstractStringBuilder.ensureCapacityInternal(
> AbstractStringBuilder.java:114)
> at java.lang.AbstractStringBuilder.append(
> AbstractStringBuilder.java:415)
> at java.lang.StringBuffer.append(StringBuffer.java:237)
> at org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.
> format(PatternParser.java:420)
> at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
> at org.apache.log4j.WriterAppender.subAppend(
> WriterAppender.java:301)
> at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
> at org.apache.log4j.AppenderSkeleton.doAppend(
> AppenderSkeleton.java:230)
> at org.apache.log4j.helpers.AppenderAttachableImpl.
> appendLoopOnAppenders(AppenderAttachableImpl.java:65)
> at org.apache.log4j.Category.callAppenders(Category.java:203)
> at org.apache.log4j.Category.forcedLog(Category.java:388)
> at org.apache.log4j.Category.info(Category.java:663)
> at org.geotools.util.logging.Log4JLogger.info(Log4JLogger.
> java:135)
> at org.geoserver.filters.LoggingFilter.doFilter(
> LoggingFilter.java:81)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:42)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.geoserver.filters.SessionDebugFilter.doFilter(
> SessionDebugFilter.java:48)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.geoserver.filters.FlushSafeFilter.doFilter(
> FlushSafeFilter.java:44)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(
> SetCharacterEncodingFilter.java:109)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.apache.catalina.core.StandardWrapperValve.invoke(
> StandardWrapperValve.java:220)
> at org.apache.catalina.core.StandardContextValve.invoke(
> StandardContextValve.java:122)
>
> First I thought that the image that I wanted to upload was too big, approx
> 260MB. But I could upload a much bigger image (700MB) without problems.
> I read a lot within the list but could not find a solution. As described
> in http://docs.geoserver.org/latest/en/user/production/
> troubleshooting.html I printed the heap status via jmap but to be honest
> I cannot read anything out of it:
>
> Attaching to process ID 2023, please wait...
> Debugger attached successfully.
> Server compiler detected.
> JVM version is 24.75-b04
>
> using thread-local object allocation.
> Parallel GC with 1 thread(s)
>
> Heap Configuration:
>MinHeapFreeRatio = 0
>MaxHeapFreeRatio = 100
>MaxHeapSize  = 3288334336 (3136.0MB)
>NewSize  = 1310720 (1.25MB)
>MaxNewSize   = 17592186044415 MB
>OldSize  = 5439488 (5.1875MB)
>NewRatio = 2
>SurvivorRatio= 8
>PermSize =

[Geoserver-users] OutOfMemoryError: Java heap space

2016-09-29 Thread Sabine Ohlendorf

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 java.util.Arrays.copyOf(Arrays.java:2367)
at 
java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)
at 
java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)
at 
java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)
at java.lang.StringBuffer.append(StringBuffer.java:237)
at 
org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.format(PatternParser.java:420)
at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
at 
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
at org.apache.log4j.Category.callAppenders(Category.java:203)
at org.apache.log4j.Category.forcedLog(Category.java:388)
at org.apache.log4j.Category.info(Category.java:663)
at org.geotools.util.logging.Log4JLogger.info(Log4JLogger.java:135)
at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:81)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:42)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.geoserver.filters.SessionDebugFilter.doFilter(SessionDebugFilter.java:48)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.geoserver.filters.FlushSafeFilter.doFilter(FlushSafeFilter.java:44)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:109)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

First I thought that the image that I wanted to upload was too big, approx 
260MB. But I could upload a much bigger image (700MB) without problems.
I read a lot within the list but could not find a solution. As described in 
http://docs.geoserver.org/latest/en/user/production/troubleshooting.html I 
printed the heap status via jmap but to be honest I cannot read anything out of 
it:

Attaching to process ID 2023, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 24.75-b04

using thread-local object allocation.
Parallel GC with 1 thread(s)

Heap Configuration:
   MinHeapFreeRatio = 0
   MaxHeapFreeRatio = 100
   MaxHeapSize  = 3288334336 (3136.0MB)
   NewSize  = 1310720 (1.25MB)
   MaxNewSize   = 17592186044415 MB
   OldSize  = 5439488 (5.1875MB)
   NewRatio = 2
   SurvivorRatio= 8
   PermSize = 21757952 (20.75MB)
   MaxPermSize  = 268435456 (256.0MB)
   G1HeapRegionSize = 0 (0.0MB)

Heap Usage:
PS Young Generation
Eden Space:
   capacity = 522190848 (498.0MB)
   used = 35361864 (33.72370147705078MB)
   free = 486828984 (464.2762985229492MB)
   6.77182760583349% used
>From Space:
   capacity = 287309824 (274.0MB)
   used = 0 (0.0MB)
   free = 287309824 (274.0MB)
   0.0% used
To Space:
   capacity = 286785536 (273.5MB)
   used = 0 (0.0MB)
   free = 286785536 (273.5MB)
   0.0% used
PS Old Generation
   capacity = 2192572416 (2091.0MB)
   used = 1492816408 (1423.6606674194336MB)
   free = 699756008 (667.3393325805664MB)
   68.08515865229238% used
PS Perm Generation
   capacity = 106954752 (102.0MB)
   used = 88507512 (84.40734100341797MB)
   free = 18447240 (17.59265899658203MB)
   82.75229510139016% used

36895 interned Strings occupying 3920704 bytes.

Can anybody help?
Thanks!
Regards, Sabine

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

2016-09-29 Thread Sabine Ohlendorf

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 clipped to the old bounding box 
> still or is it simply Geoserver's preview that's going stale when you chance 
> the bbox?
> 
> - Patrick O'Toole
> 

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] How many layers/resources per store?

2016-09-29 Thread Peter Kovac


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 will work happily with it.


In my opinion setting up JNDI manually is just a small effort for a very 
high reward.



Cheers,

Peter


On 28. 9. 2016 10:40, Anton Lundkvist wrote:

Ok thanks!

I'm relying heavily on gsconfig.py 
https://github.com/boundlessgeo/gsconfig for publishing my tables. I 
haven't found any info on if it is possible to use JNDI with gsconfig. 
Does anyone know?


regards,

anton

2016-09-28 9:15 GMT+02:00 Peter Kovac >:


Hi Anton,

If you are using Apache Tomcat or another container I recommend
using JNDI connection pooling. That way you have 1 connection pool
shared among all of your layers and you can manage it easily. I
observed significant performance gains when switching from
"PostGIS" to "PostGIS (JNDI)" type of store (database connections
don't have to be recreated with each request and it saves a lot of
time). It works with ImageMosaic datastores with custom dimensions
too.


http://docs.geoserver.org/stable/en/user/tutorials/tomcat-jndi/tomcat-jndi.html




Cheers,

Peter


On 28. 9. 2016 8:57, Anton Lundkvist wrote:

Hi GeoServer Users:

I'm using GeoServer for serving vector data (from PostGis).
Keeping the number of stores down e.g. many layers per store
reduces the number of connections to PostGis. This is desirable
as I have hundreds of tables that are published through GeoServer.

 Is there a recommended limit for how many layers / resources I
should handle with one store?

Regards,

Anton Lundkvist





--

___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geoserver-users



-- 
Peter Kovac

IMS Programmer
MicroStep-MIS
peter.ko...@microstep-mis.com 

--
---
Anton Lundkvist
Malmö
Tel:0046 768 847 703

--
Peter Kovac
IMS Programmer
MicroStep-MIS
peter.ko...@microstep-mis.com
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

Re: [Geoserver-users] OutOfMemoryError: Java heap space

Re: [Geoserver-users] OutOfMemoryError: Java heap space

[Geoserver-users] OutOfMemoryError: Java heap space

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

Re: [Geoserver-users] How many layers/resources per store?

7 matches

Site Navigation

Mail list logo

Footer information