Re: [Geoserver-users] geoserver specs

2017-12-20 Thread bradh 
"It depends" - workload, data types, tile caching and a lot of other things
you haven't described.

 

I'd suggest working through the
http://docs.geoserver.org/latest/en/user/production/index.html#production
page, because the memory use is dependent on how you configure / deploy it;
and there are a lot of important things to configure other than just memory.
There is are recommended settings in there for heap, but I'd be cautious
about blindly setting that without reading the rest of the page, and
consider what other settings you might need.

 

Brad

 

From: Bessette-Halsema, Dominique E [mailto:dominique.besse...@gdit.com] 
Sent: Thursday, 21 December 2017 11:27 AM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] geoserver specs

 

Hi I'm trying to find the documentation for the recommended amount of memory
to run GeoServer

 

Thanks!

Dominique Bessette

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

[Geoserver-users] geoserver specs

2017-12-20 Thread Bessette-Halsema, Dominique E 
Hi I'm trying to find the documentation for the recommended amount of memory to 
run GeoServer



Thanks!

Dominique Bessette



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] Geoserver WFS - app-schema plugin - java.lang.StackOverflowErrors

2017-12-20 Thread Ben Caradoc-Davies 

Davor,

the XSLT is applied after the response has been encoded to XML. The size 
of the response will be affected by maxFeatures/count but not I think by 
the database fetch size. Pagination is applied at the WFS level with 
startIndex (WFS 2.0, supported in GeoServer WFS 1.1.0 as an extension).


The stack trace of the failing request will help us investigate the problem.

Kind regards,
Ben.

On 20/12/17 22:59, Davor Racic wrote:

Hi Ben & Nuno, thank you for your suggestions.

things seem a little bit clearer. We are testing INSPIRE download service,
not an application, so we assume that someone can and should be able to
download/transfer whole set of data (cca 13 features). I suppose some
sort of pagination should be done by Geoserver itself in background when
data PG store is configured with some value set on "fetch size", and
suppose that this XLST post-processing is done page by page after each
fetch? In our case, that property was missing in app-schema store
definition. We are testing this at the moment.

Best regards
Davor

sri, 20. pro 2017. u 00:12 Ben Caradoc-Davies  napisao je:


Davor,

GeoServer uses XSLT to post-process WFS responses (and halve the number
of database queries). Do you have the other end of the stack trace so we
can see the origin and confirm this as the cause? Try *reducing* your
stack size to make the trace shorter.

It looks like this failure might be caused by the Xalan XSLT embedded in
the JVM standard library using Quicksort to sort an array of integers.
Quicksort is a terrible algorithm because its worst-case performance is
O(n**2):
https://en.wikipedia.org/wiki/Quicksort

Some Quicksort implementations can exhibit this behaviour when the input
is already sorted, already reverse-sorted, or all inputs are the same
(first two criteria combined). Recursive implementations will then use
O(n**2) time and stack.

Heapsort is often preferred because its worst-case performance is O(n
log n):
https://en.wikipedia.org/wiki/Heapsort

Kind regards,
Ben.

On 20/12/17 03:41, Davor Racic wrote:

I'm using Geoserver 2.11.dev and app-schema plugin. WFS max request limit
is set to 1mil features. When serving large WFS 2.0 requests (over 10
fetures) from app-schema store (PostGIS backend) requests fail with

error:


19 pro 09:49:48 ERROR [geoserver.ows] -
java.lang.StackOverflowError
 at


com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:162)


 at


com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:163)


 at


com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:163)


 at


com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:163)

 ...

Serving smaller set of features (<10) doesn't cause any error. When I
set maximum thread stack size for JAVA in JAVA_OPTS to -Xss4096K, errors
disappear, but I'm still wondering why this setting is necessary. Any

idea?

Can something like reprojection cause this?

Best regards
Davor





--

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to

this list:

- Earning your support instead of buying it, but Ian Turton:

http://www.ianturton.com/talks/foss4g.html#/

- The GeoServer user list posting guidelines:

http://geoserver.org/comm/userlist-guidelines.html


If you want to request a feature or an improvement, also see this:

https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer



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



--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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



--
Ben

Re: [Geoserver-users] Geoserver WFS - app-schema plugin - java.lang.StackOverflowErrors

2017-12-20 Thread Ben Caradoc-Davies 
For the record, I made one small mistake here: for stack-based recursive 
implementations, worst case Quicksort is O(n**2) time and O(n) stack. By 
comparison, worst case Heapsort is O(n log n) time and O(log n) stack.


Kind regards,
Ben.

On 20/12/17 12:12, Ben Caradoc-Davies wrote:
It looks like this failure might be caused by the Xalan XSLT embedded in 
the JVM standard library using Quicksort to sort an array of integers. 
Quicksort is a terrible algorithm because its worst-case performance is 
O(n**2):

https://en.wikipedia.org/wiki/Quicksort

Some Quicksort implementations can exhibit this behaviour when the input 
is already sorted, already reverse-sorted, or all inputs are the same 
(first two criteria combined). Recursive implementations will then use 
O(n**2) time and stack.


Heapsort is often preferred because its worst-case performance is O(n 
log n):

https://en.wikipedia.org/wiki/Heapsort


--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

[Geoserver-users] Edit layer: Publishing: Edit Layer is missing

2017-12-20 Thread sulu 
Hi.

Maybe I'm a little dumb but i cannot find "Edit Layer" in the publishing
tab.
I am using GS 12.1. 
Is there some Config-Option to turn this on?

Thanks
Andy




--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] Problem Import wfs from Mapserver in Web Feature Server (NG) Geoserver

2017-12-20 Thread Andrea Aime 
On Wed, Dec 20, 2017 at 2:14 PM, geomatick  wrote:

> Just WFS 1.0.0 enables to create the store with the URL Mapserver provider.
>
> So I understand that there is no solution?
>

I can't tell you without spending more time analyzing the issue (time that
I don't have right now, sorry...)
but if you can configure the layer and view them in 1.0 but not 1.1 and 2.0
it might be an axis flipping
issue, mapserver has had issues with it in the past (I thought they were
fixed, but who knows, maybe
it's configuration dependent or that is an older version).

To handle server that do not respect axis flipping according to
specification there are two axis
order controls in the store configuration, you can try to play with them
and see if one particular combination
makes it work

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 di Montramito 3/A
55054  Massarosa (LU)
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.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] Problem Import wfs from Mapserver in Web Feature Server (NG) Geoserver

2017-12-20 Thread geomatick 
Hi Andrea,

Thank's for your return.

Yes I tried the different versions of WFS 1.0.0, 1.1.0, 2.0.0.

Just WFS 1.0.0 enables to create the store with the URL Mapserver provider.

So I understand that there is no solution?

Florian



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

[Geoserver-users] Problem Import wfs from Mapserver in Web Feature Server (NG) Geoserver

2017-12-20 Thread geomatick 
Hi,

I m trying to create a layer in Web Feature Server (NG) store from wfs
Mapserver.

The provider informs the URL wfs Mapserver as :
http://ogc.geo-ide.developpement-durable.gouv.fr/wxs?map=/opt/data/carto/geoide-catalogue/1.4/org_38102/811a8b21-2526-4eb9-bfaf-ffe61175a313.internet.map

So I update it to get the projection and the GetCapabilities as :
http://ogc.geo-ide.developpement-durable.gouv.fr/wxs?map=/opt/data/carto/geoide-catalogue/1.4/org_38102/811a8b21-2526-4eb9-bfaf-ffe61175a313.internet.map=WFS=2.0.0=GetCapabilities=epsg:4326

In web navigator, there is no matter and in QGIS I succeed to import the
layer.

To import the data in geoserver, I create a Web Feature Server (NG) store
like in this tutorial of Geo-solutions
http://geoserver.geo-solutions.it/edu/en/adding_data/add_wfscascade.html and
I publish the layer.

Unfortunately, It s impossible to display the layer.

Could you help me please?

Thank's for your return.

Florian



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] Geoserver WFS - app-schema plugin - java.lang.StackOverflowErrors

2017-12-20 Thread Davor Racic 
Hi Ben & Nuno, thank you for your suggestions.

things seem a little bit clearer. We are testing INSPIRE download service,
not an application, so we assume that someone can and should be able to
download/transfer whole set of data (cca 13 features). I suppose some
sort of pagination should be done by Geoserver itself in background when
data PG store is configured with some value set on "fetch size", and
suppose that this XLST post-processing is done page by page after each
fetch? In our case, that property was missing in app-schema store
definition. We are testing this at the moment.

Best regards
Davor

sri, 20. pro 2017. u 00:12 Ben Caradoc-Davies  napisao je:

> Davor,
>
> GeoServer uses XSLT to post-process WFS responses (and halve the number
> of database queries). Do you have the other end of the stack trace so we
> can see the origin and confirm this as the cause? Try *reducing* your
> stack size to make the trace shorter.
>
> It looks like this failure might be caused by the Xalan XSLT embedded in
> the JVM standard library using Quicksort to sort an array of integers.
> Quicksort is a terrible algorithm because its worst-case performance is
> O(n**2):
> https://en.wikipedia.org/wiki/Quicksort
>
> Some Quicksort implementations can exhibit this behaviour when the input
> is already sorted, already reverse-sorted, or all inputs are the same
> (first two criteria combined). Recursive implementations will then use
> O(n**2) time and stack.
>
> Heapsort is often preferred because its worst-case performance is O(n
> log n):
> https://en.wikipedia.org/wiki/Heapsort
>
> Kind regards,
> Ben.
>
> On 20/12/17 03:41, Davor Racic wrote:
> > I'm using Geoserver 2.11.dev and app-schema plugin. WFS max request limit
> > is set to 1mil features. When serving large WFS 2.0 requests (over 10
> > fetures) from app-schema store (PostGIS backend) requests fail with
> error:
> >
> > 19 pro 09:49:48 ERROR [geoserver.ows] -
> > java.lang.StackOverflowError
> > at
> >
> com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:162)
> >
> > at
> >
> com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:163)
> >
> > at
> >
> com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:163)
> >
> > at
> >
> com.sun.org.apache.xalan.internal.xsltc.util.IntegerArray.quicksort(IntegerArray.java:163)
> > ...
> >
> > Serving smaller set of features (<10) doesn't cause any error. When I
> > set maximum thread stack size for JAVA in JAVA_OPTS to -Xss4096K, errors
> > disappear, but I'm still wondering why this setting is necessary. Any
> idea?
> > Can something like reprojection cause this?
> >
> > Best regards
> > Davor
> >
> >
> >
> >
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >
> >
> >
> > ___
> > Geoserver-users mailing list
> >
> > Please make sure you read the following two resources before posting to
> this list:
> > - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> > - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> >
> > If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
> >
> >
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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