Re: [Geoserver-users] How to map the same feature from alternate data sources in WFS

[Humphries, Graham]

Hi Michael,

That looks to me like you have a one-to-many relationship between your building 
and its tax assessments. The building layer, presumably, has the spatial 
component and the tax assessments are attributes add to the building feature by 
a join.

What you are describing sounds like you want the user to click a checkbox on an 
interface, to toggle between the full/ abridged dataset. I think you will need 
to write some code to do that.

From: Stein, Michael P [US] (TS) [mailto:mike.st...@ngc.com]
Sent: Friday, 15 May 2020 10:37 AM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] How to map the same feature from alternate data 
sources in WFS


We do not treat the historic data as a separate feature from the current data. 
There is only one instance of the top-level feature, no matter how much history 
it has. All its history is _internal_ to the one and only instance of the 
feature. What we want is for the user to be able to choose an abridged version 
of the feature, or an unabridged version of the feature, in response to exactly 
the same filter.

Let's say we have buildings as a feature, and buildings are of various types - 
offices, flats, stores, warehouses, etc. Part of the data for a feature is its 
valuation for tax purposes. Below is a building built in 2017, in unabridged 
form showing all tax assessment history attached to the building:


   
   123 Main St
  Mytown
   
   Office
   
  
  2017
  9
  2018-01-01
  
  
  2018
  92000
  2019-01-01
  
  
  2019
  96000
  2020-01-01
  
  
  2020
  99000
  



Sometimes I really do want the above unabridged form for every 
BuildingType=Office in my database. The filter below will do it:


  
 BuildingType
 Office
  
   

Other times, however, I am not interested in the history. All I want is the 
abridged form below, representing just the current year for every Office:


   
   123 Main St
  Mytown
   
   Office
   
  
  2020
  99000
  




How can I get GeoServer to give me my choice of the two results? I have even 
added your DateArchived. What filter would give me the second, abridged format 
for all my office buildings?

What you are suggesting would work if our output looked like this:


   
   123 Main St
  Mytown
   
   Office
  
  2017
  9
  


   
   123 Main St
  Mytown
   
   Office
  
  2018
  92000
  


   
   123 Main St
  Mytown
   
   Office
  
  2019
  96000
  


   
   123 Main St
  Mytown
   
   Office
  
  2020
  99000
  


Then I could filter on both the building type and the tax year, and get the 
combination of Office and tax year 2020. Unfortunately, that is not the schema 
definition we are using.

From: Humphries, Graham 
mailto:graham.humphr...@stategrowth.tas.gov.au>>
Sent: Thursday, May 14, 2020 19:54
To: Stein, Michael P [US] (TS) mailto:mike.st...@ngc.com>>
Cc: 
geoserver-users@lists.sourceforge.net
Subject: EXT :RE: How to map the same feature from alternate data sources in WFS

Probably should keep the discussion on the list. Other people might have a 
better understanding of your problem than me.

The way we handle our historic data is by having a date_archived field in the 
table. If the data is current the date_archived value is null. When this record 
is suprceded the date_archived is populated with the date when this occurs.

This makes filtering historic and current data simple ie: date_archived is null 
or date_archived is not null.

From: Stein, Michael P [US] (TS) [mailto:mike.st...@ngc.com]
Sent: Friday, 15 May 2020 12:42 AM
To: Humphries, Graham 
mailto:graham.humphr...@stategrowth.tas.gov.au>>
Subject: RE: How to map the same feature from alternate data sources in WFS

(I am responding to you directly, not the list.)

I am not entirely sure where you are suggesting this filtering be established. 
We could certainly post-process the existing output to remove all but the 
current detail record, but that would be a significant performance hit. We want 
the filtering to be done in the initial SQL query for maximum performance.

We could also stand up a separate instance of GeoServer with the alternative 
mappings, but the customer is not going to be happy with the idea of buying 
additional system capacity to support that solution.

If you are suggesting adding the filter to the request, there are two problems 
with this. One problem is that we do not want to burden the end user with the 
task of creating a complex filter that they must remember to edit every time 
they run it to put in a new value corresponding to "today". The stickier 

Re: [Geoserver-users] GeoS 2.17.0 problem removing layers

[Tom S]

Perhaps revise the 'GeoServer Cleanup'  section to say something like

Under Java8, if the Native JAI functions are installed (see below) , you 
may optionally remove the original JAI files from the GeoServer 
|WEB-INF/lib| folder:


As-is, the implication is that everyone should do this (as I tried)


On 5/14/2020 5:56 PM, Jody Garnett wrote:
Those JAI jars are only available to install in Java 8 (as it uses the 
old java plugin system and is not compatible with the java module 
system introduced in Java 9 onward).
Please only remove those jars if you have installed the JAI plugin 
into Java 8, and thus GeoServer does not need its own copy.


___
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] GeoS 2.17.0 problem removing layers

[Jody Garnett]

Those JAI jars are only available to install in Java 8 (as it uses the old
java plugin system and is not compatible with the java module system
introduced in Java 9 onward).
Please only remove those jars if you have installed the JAI plugin into
Java 8, and thus GeoServer does not need its own copy.

The documentation is here:
https://docs.geoserver.org/latest/en/user/production/java.html

If you have any feedback on how we can make this more clear please let me
know how it can be improved (as setup trouble is very frustrating).

On Wed, May 13, 2020 at 4:47 PM Tom S  wrote:

> Things work as expected under an older system with Tomcat 8 and JRE 1.8.
>
> Also, while reviewing and doing the 'GeoServer cleanup' task (remove
> jai* jars) found on
>
> https://docs.geoserver.org/stable/en/user/production/java.html#production-java
>
> for 1.17.0, the program will no longer run properly (in the new
> environment).
>
>
> On 5/13/2020 4:15 PM, Tom S wrote:
> > I will double check that, but the problem exists even with the default
> > data set.  I also see the same issue under Chrome and with GeoS
> > V1.16.2.  The test system I am using has the latest tomcat 9.x and
> > AdoptOpenJDK 11.x - I might try it on a different system with JDK 8.
> >
>
>
> ___
> 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 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] How to map the same feature from alternate data sources in WFS

[Stein, Michael P [US] (TS)]

We do not treat the historic data as a separate feature from the current data. 
There is only one instance of the top-level feature, no matter how much history 
it has. All its history is _internal_ to the one and only instance of the 
feature. What we want is for the user to be able to choose an abridged version 
of the feature, or an unabridged version of the feature, in response to exactly 
the same filter.

Let's say we have buildings as a feature, and buildings are of various types - 
offices, flats, stores, warehouses, etc. Part of the data for a feature is its 
valuation for tax purposes. Below is a building built in 2017, in unabridged 
form showing all tax assessment history attached to the building:


   
   123 Main St
  Mytown
   
   Office
   
  
  2017
  9
  2018-01-01
  
  
  2018
  92000
  2019-01-01
  
  
  2019
  96000
  2020-01-01
  
  
  2020
  99000
  



Sometimes I really do want the above unabridged form for every 
BuildingType=Office in my database. The filter below will do it:


  
 BuildingType
 Office
  
   

Other times, however, I am not interested in the history. All I want is the 
abridged form below, representing just the current year for every Office:


   
   123 Main St
  Mytown
   
   Office
   
  
  2020
  99000
  




How can I get GeoServer to give me my choice of the two results? I have even 
added your DateArchived. What filter would give me the second, abridged format 
for all my office buildings?

What you are suggesting would work if our output looked like this:


   
   123 Main St
  Mytown
   
   Office
  
  2017
  9
  


   
   123 Main St
  Mytown
   
   Office
  
  2018
  92000
  


   
   123 Main St
  Mytown
   
   Office
  
  2019
  96000
  


   
   123 Main St
  Mytown
   
   Office
  
  2020
  99000
  


Then I could filter on both the building type and the tax year, and get the 
combination of Office and tax year 2020. Unfortunately, that is not the schema 
definition we are using.

From: Humphries, Graham 
Sent: Thursday, May 14, 2020 19:54
To: Stein, Michael P [US] (TS) 
Cc: geoserver-users@lists.sourceforge.net
Subject: EXT :RE: How to map the same feature from alternate data sources in WFS

Probably should keep the discussion on the list. Other people might have a 
better understanding of your problem than me.

The way we handle our historic data is by having a date_archived field in the 
table. If the data is current the date_archived value is null. When this record 
is suprceded the date_archived is populated with the date when this occurs.

This makes filtering historic and current data simple ie: date_archived is null 
or date_archived is not null.

From: Stein, Michael P [US] (TS) [mailto:mike.st...@ngc.com]
Sent: Friday, 15 May 2020 12:42 AM
To: Humphries, Graham 
mailto:graham.humphr...@stategrowth.tas.gov.au>>
Subject: RE: How to map the same feature from alternate data sources in WFS

(I am responding to you directly, not the list.)

I am not entirely sure where you are suggesting this filtering be established. 
We could certainly post-process the existing output to remove all but the 
current detail record, but that would be a significant performance hit. We want 
the filtering to be done in the initial SQL query for maximum performance.

We could also stand up a separate instance of GeoServer with the alternative 
mappings, but the customer is not going to be happy with the idea of buying 
additional system capacity to support that solution.

If you are suggesting adding the filter to the request, there are two problems 
with this. One problem is that we do not want to burden the end user with the 
task of creating a complex filter that they must remember to edit every time 
they run it to put in a new value corresponding to "today". The stickier 
problem is that a filter is a filter on the feature as a whole, not on 
sub-elements of the feature. Any feature that has one detail item that matches 
the filter on detail items will bring back all the detail. Using my example 
feature, if I were to filter for color red in the request as follows:


  
 
myns:FeatureDetails/myns:FeatureDetail/myns:color
 red
  
   

it is interpreted as "return any feature having at least one detail with the 
color red". The feature as a whole is considered a match and the feature as a 
whole comes back in the response, including the green detail.

If you are suggesting something other than the above, please explain in more 
detail.

From: Humphries, Graham 

Re: [Geoserver-users] Automatic refresh GeoServer

[Jody Garnett]

Good afternoon Diego:

My employer GeoCat is one of those listed for GeoServer commercial support
 and we would of course love an opportunity
to work with you.

If you would like to contact myself as a member of the GeoServer community
please do so via the user list (CCed) as outlined on the GeoServer community
support  page. As a project GeoServer likes to
encourage community participation and you can help by asking questions in
public where more participants have a chance to answer your question and
learn from each others discussion.

Please ensure you have read through the post guidelines
 before sending email
to the user list.
--
Jody Garnett


On Wed, 13 May 2020 at 12:59, Diego Fernández García 
wrote:

> Hi!
> My name is Diego Fernández and I live in Spain.
> I use GeoServer and PostGIS to publish WMS services. I have an automatic
> system to load points, lines and polygons. Currently, to see that new
> information, I have to refresh the WMS url.
> Do you know of any way to automate the refreshing of the URL every time a
> new record is created in the database?
> Thanks and regards,
> Diego
>
___
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] How to map the same feature from alternate data sources in WFS

[Humphries, Graham]

Probably should keep the discussion on the list. Other people might have a 
better understanding of your problem than me.

The way we handle our historic data is by having a date_archived field in the 
table. If the data is current the date_archived value is null. When this record 
is suprceded the date_archived is populated with the date when this occurs.

This makes filtering historic and current data simple ie: date_archived is null 
or date_archived is not null.

From: Stein, Michael P [US] (TS) [mailto:mike.st...@ngc.com]
Sent: Friday, 15 May 2020 12:42 AM
To: Humphries, Graham 
Subject: RE: How to map the same feature from alternate data sources in WFS

(I am responding to you directly, not the list.)

I am not entirely sure where you are suggesting this filtering be established. 
We could certainly post-process the existing output to remove all but the 
current detail record, but that would be a significant performance hit. We want 
the filtering to be done in the initial SQL query for maximum performance.

We could also stand up a separate instance of GeoServer with the alternative 
mappings, but the customer is not going to be happy with the idea of buying 
additional system capacity to support that solution.

If you are suggesting adding the filter to the request, there are two problems 
with this. One problem is that we do not want to burden the end user with the 
task of creating a complex filter that they must remember to edit every time 
they run it to put in a new value corresponding to "today". The stickier 
problem is that a filter is a filter on the feature as a whole, not on 
sub-elements of the feature. Any feature that has one detail item that matches 
the filter on detail items will bring back all the detail. Using my example 
feature, if I were to filter for color red in the request as follows:


  
 
myns:FeatureDetails/myns:FeatureDetail/myns:color
 red
  
   

it is interpreted as "return any feature having at least one detail with the 
color red". The feature as a whole is considered a match and the feature as a 
whole comes back in the response, including the green detail.

If you are suggesting something other than the above, please explain in more 
detail.

From: Humphries, Graham 
mailto:graham.humphr...@stategrowth.tas.gov.au>>
Sent: Wednesday, May 13, 2020 18:19
To: Stein, Michael P [US] (TS) mailto:mike.st...@ngc.com>>; 
geoserver-users@lists.sourceforge.net
Subject: EXT :RE: How to map the same feature from alternate data sources in WFS

Couldn't you duplicate the feature set with a filter to only show the current 
data?

From: Stein, Michael P [US] (TS) [mailto:mike.st...@ngc.com]
Sent: Thursday, 14 May 2020 3:20 AM
To: 
geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] How to map the same feature from alternate data 
sources in WFS

We are currently in the process of upgrading from Geoserver 2.10 to 2.16; what 
follows is from our 2.10 installation.

We have a feature that carries historic detail. Our current mapping returns an 
XML representation of the feature containing all of the historic detail. E.g.,


 < myns:FeatureIdentification>...
 < myns:FeatureDetails>
 < myns:FeatureDetail>
  < myns:StartDate>2015-08-20
  < myns:EndDate>2016-03-01
  < myns:color>red
  < myns:cost>3.99
  
 < myns:FeatureDetail>
  < myns:StartDate>2016-03-02
  < myns:EndDate>2018-12-15
  < myns:color>green
  < myns:cost>3.99
  
  
 < myns:FeatureDetail>
  < myns:StartDate>2018-12-16
  < myns:EndDate/>
  < myns:color>red
  < myns:cost>4.29
  


Sometimes we want this complete historical record, but other times we want to 
omit the history and return only the detail currently in effect - the detail 
with a start date of 2018-12-16 in the example above. I thought to do this by 
adding an element TheFeatureCurrent to the XML schema and to GeoServer mapping. 
Like TheFeature, it is defined as being of TheFeatureType. I then added a 
mapping for TheFeatureCurrent as a copy of the mapping for TheFeature, except 
that instead of the table FEATURE_DETAIL, the database source for the detail 
would be a view FEATURE_DETAIL_CURRENT_VIEW that restricted the detail to just 
those rows covering the current date. Although the mapping file was ostensibly 
for TheFeatureCurrent, the new mapping file actually mapped to the same 
TheFeature element rather than TheFeatureCurrent.

I discovered that I needed to modify all the mapping names in the new mapping 
file to not match the mapping names in the mapping file for the original 
feature. If I did not do that, I got errors like

java.lang.RuntimeException: 

Re: [Geoserver-users] GeoS 2.17.0 problem removing layers

[Tom S]

Yes - at first glance any of the 'bookmarkable' URL calls will fail.  
Its working for me if I remove the tomcat 'proxy*' directives.  I know I 
had to add them at some point in the past (with much older versions of 
httpd, tomcat and geoserver) to get things to work, but so far it seems 
fine without them.


I'll try to find out how/where to submit an official bug report shortly.


On 5/14/2020 4:12 PM, Humphries, Graham wrote:


I can see the same error when accessing Geoserver through httpd. BTW I 
am running Geoserver on Solaris.


It looks like a security issue where the request url  does not match 
the destination url. A submit request returns a 400 Bad Request 
response in the browser.


I just tried enabling CORS in the geoserver web.xml, but this made no 
difference.



___
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] GeoS 2.17.0 problem removing layers

[Humphries, Graham]

I can see the same error when accessing Geoserver through httpd. BTW I am 
running Geoserver on Solaris.

It looks like a security issue where the request url  does not match the 
destination url. A submit request returns a 400 Bad Request response in the 
browser.

I just tried enabling CORS in the geoserver web.xml, but this made no 
difference.

From: Tom S [mailto:tom-sourcefo...@tomsaul.com]
Sent: Friday, 15 May 2020 7:46 AM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] GeoS 2.17.0 problem removing layers


So a bit more info.  This problem seems to occur at any point if the tomcat 
Connector definition includes proxyName and proxyPort definitions (even if they 
just point to localhost:x).  Even if you access the instance directly (not via 
proxy), and the proxy settings point to it directly it happens.  The issue 
shows up on all the 'Data' screens I have tried.

Problems also occur is you try to save settings, which show an error like

-

Type Status Report

Message Origin does not correspond to request

Description The server cannot or will not process the request due to something 
that is perceived to be a client error (e.g., malformed request syntax, invalid 
request message framing, or deceptive request routing).

-

There are no relevant messages showing up in the tomcat or geoserver logs at 
production logging level.  If I turn on verbose logging I get the following

2020-05-14 11:41:01,480 DEBUG 
[security.IncludeQueryStringAntPathRequestMatcher] - Checking match of request 
: 'Path: /web/wicket/bookmarkable/org.geoserver.web.data.layer.layerpage, 
QueryString: 
16-2.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll=false';
 against '/web/**'
2020-05-14 11:41:01,480 DEBUG 
[security.IncludeQueryStringAntPathRequestMatcher] - Matched Path: 
/web/wicket/bookmarkable/org.geoserver.web.data.layer.layerpage, QueryString: 
16-2.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll=false
 with /web/**
2020-05-14 11:41:01,480 DEBUG [geoserver.ows] - Could not find a layer group 
named web
2020-05-14 11:41:01,480 DEBUG [geoserver.ows] - Could not find a layer group 
named web
2020-05-14 11:41:01,496 DEBUG [geoserver.ows] - Could not find a layer group 
named web
2020-05-14 11:41:01,496 DEBUG [geoserver.ows] - Could not find a layer group 
named web
2020-05-14 11:41:01,636 DEBUG [org.geoserver] - Thread 89 locking in mode READ

On 5/14/2020 11:52 AM, Tom S wrote:
Glad to see this is reproducible (on a non-Windows platform even).  I'm still 
trying to track it down, but for me this seems to be related to using a Apache 
HTTPD (latest version) proxy as a front end.  From that programs access logs I 
see



CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by 
legal professional privilege, and is intended only for the person or persons to 
whom it is addressed. If you are not such a person, you are warned that any 
disclosure, copying or dissemination of the information is unauthorised. If you 
have received the transmission in error, please immediately contact this office 
by telephone, fax or email, to inform us of the error and to enable 
arrangements to be made for the destruction of the transmission, or its return 
at our cost. No liability is accepted for any unauthorised use of the 
information contained in this transmission.
___
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] GeoS 2.17.0 problem removing layers

[Humphries, Graham]

Hi Tom,

You are probably right about httpd.  I have always bypassed httpd to access the 
Geoserver web interface. I have just done it now on our production environment 
and the select all did not work.

Our system is set to recognise an external network request or an internal 
network request and logs you on as one of two users automatically. Neither of 
these users have admin rights to the interface, so the problem might be about 
the users privileges.

-Original Message-
From: Tom S [mailto:tom-sourcefo...@tomsaul.com]
Sent: Friday, 15 May 2020 4:53 AM
To: Russ Hore 
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] GeoS 2.17.0 problem removing layers

Glad to see this is reproducible (on a non-Windows platform even).  I'm still 
trying to track it down, but for me this seems to be related to using a Apache 
HTTPD (latest version) proxy as a front end.  From that programs access logs I 
see

::1 - - [13/May/2020:14:49:09 -1000] "POST 
/geoserver/web/wicket/bookmarkable/org.geoserver.web.data.layer.LayerPage?5-7.IBehaviorListener.0-table-listContainer-items-153-selectItemContainer-selectItem
HTTP/1.1" 400 492
::1 - - [13/May/2020:14:49:11 -1000] "POST 
/geoserver/web/wicket/bookmarkable/org.geoserver.web.data.layer.LayerPage?5-7.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll
HTTP/1.1" 400 492

If I bypass the proxy it seems to be working (but I have not fully tested).  
The problem exists for me with every combination of COTS (geoS, tomcat) I have 
used so far.

Functionally everything else seems OK so far - its just this specific pair of 
functions that are broken.


On 5/14/2020 1:49 AM, Russ Hore wrote:
> I have GS2.17.0 (running on one of 4 Ubuntu 20.04 VMs behind Apache
> running on the host also Ubuntu 20.04)  and I found the Select All
> check box does not check all the boxes beneath it on the Stores form.
> (If that is what you mean)
>
>


___
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: 
https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ianturton.com%2Ftalks%2Ffoss4g.html%23%2Fdata=02%7C01%7CGraham.Humphries%40stategrowth.tas.gov.au%7Cce1f6e1ec6e14984abcc08d7f8386016%7C64ebab8accf44b5ca2d32b4e972d96b2%7C0%7C0%7C63725079682363sdata=XYoP%2BCVxuRx%2BnMKPHom3cl0F5YoCwLqiQovZtOQf7P4%3Dreserved=0
- The GeoServer user list posting guidelines: 
https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgeoserver.org%2Fcomm%2Fuserlist-guidelines.htmldata=02%7C01%7CGraham.Humphries%40stategrowth.tas.gov.au%7Cce1f6e1ec6e14984abcc08d7f8386016%7C64ebab8accf44b5ca2d32b4e972d96b2%7C0%7C0%7C63725079682363sdata=f3XWuJ89YOzxpes0V7lawLoe17UAkjiKH%2FTgtBAKIRE%3Dreserved=0

If you want to request a feature or an improvement, also see this: 
https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgeoserver%2Fgeoserver%2Fwiki%2FSuccessfully-requesting-and-integrating-new-features-and-improvements-in-GeoServerdata=02%7C01%7CGraham.Humphries%40stategrowth.tas.gov.au%7Cce1f6e1ec6e14984abcc08d7f8386016%7C64ebab8accf44b5ca2d32b4e972d96b2%7C0%7C0%7C63725079682363sdata=CEPqfqI8yHvIsn9gXxSj6Reo6kIsmoFEiJMypl893IE%3Dreserved=0


Geoserver-users@lists.sourceforge.net
https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fgeoserver-usersdata=02%7C01%7CGraham.Humphries%40stategrowth.tas.gov.au%7Cce1f6e1ec6e14984abcc08d7f8386016%7C64ebab8accf44b5ca2d32b4e972d96b2%7C0%7C0%7C63725079682363sdata=9hAM3yVTIHAy6QdNJasq66JkvBNC1hm8H7DnE9iWIwE%3Dreserved=0



CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by 
legal professional privilege, and is intended only for the person or persons to 
whom it is addressed. If you are not such a person, you are warned that any 
disclosure, copying or dissemination of the information is unauthorised. If you 
have received the transmission in error, please immediately contact this office 
by telephone, fax or email, to inform us of the error and to enable 
arrangements to be made for the destruction of the transmission, or its return 
at our cost. No liability is accepted for any unauthorised use of the 
information contained in this transmission.


___
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: 

Re: [Geoserver-users] GeoS 2.17.0 problem removing layers

[Tom S]

So a bit more info.  This problem seems to occur at any point if the 
tomcat Connector definition includes proxyName and proxyPort definitions 
(even if they just point to localhost:x).  Even if you access the 
instance directly (not via proxy), and the proxy settings point to it 
directly it happens.  The issue shows up on all the 'Data' screens I 
have tried.


Problems also occur is you try to save settings, which show an error like

*-
*

*Type* Status Report

*Message* Origin does not correspond to request

*Description* The server cannot or will not process the request due to 
something that is perceived to be a client error (e.g., malformed 
request syntax, invalid request message framing, or deceptive request 
routing).


-

There are no relevant messages showing up in the tomcat or geoserver 
logs at production logging level.  If I turn on verbose logging I get 
the following


2020-05-14 11:41:01,480 DEBUG 
[security.IncludeQueryStringAntPathRequestMatcher] - Checking match of 
request : 'Path: 
/web/wicket/bookmarkable/org.geoserver.web.data.layer.layerpage, 
QueryString: 
16-2.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll=false'; 
against '/web/**'
2020-05-14 11:41:01,480 DEBUG 
[security.IncludeQueryStringAntPathRequestMatcher] - Matched Path: 
/web/wicket/bookmarkable/org.geoserver.web.data.layer.layerpage, 
QueryString: 
16-2.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll=false 
with /web/**
2020-05-14 11:41:01,480 DEBUG [geoserver.ows] - Could not find a layer 
group named web
2020-05-14 11:41:01,480 DEBUG [geoserver.ows] - Could not find a layer 
group named web
2020-05-14 11:41:01,496 DEBUG [geoserver.ows] - Could not find a layer 
group named web
2020-05-14 11:41:01,496 DEBUG [geoserver.ows] - Could not find a layer 
group named web
2020-05-14 11:41:01,636 DEBUG [org.geoserver] - Thread 89 locking in 
mode READ



On 5/14/2020 11:52 AM, Tom S wrote:
Glad to see this is reproducible (on a non-Windows platform even).  
I'm still trying to track it down, but for me this seems to be related 
to using a Apache HTTPD (latest version) proxy as a front end. From 
that programs access logs I see


___
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] GeoS 2.17.0 problem removing layers

[Tom S]

Glad to see this is reproducible (on a non-Windows platform even).  I'm 
still trying to track it down, but for me this seems to be related to 
using a Apache HTTPD (latest version) proxy as a front end.  From that 
programs access logs I see


::1 - - [13/May/2020:14:49:09 -1000] "POST 
/geoserver/web/wicket/bookmarkable/org.geoserver.web.data.layer.LayerPage?5-7.IBehaviorListener.0-table-listContainer-items-153-selectItemContainer-selectItem 
HTTP/1.1" 400 492
::1 - - [13/May/2020:14:49:11 -1000] "POST 
/geoserver/web/wicket/bookmarkable/org.geoserver.web.data.layer.LayerPage?5-7.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll 
HTTP/1.1" 400 492


If I bypass the proxy it seems to be working (but I have not fully 
tested).  The problem exists for me with every combination of COTS 
(geoS, tomcat) I have used so far.


Functionally everything else seems OK so far - its just this specific 
pair of functions that are broken.



On 5/14/2020 1:49 AM, Russ Hore wrote:
I have GS2.17.0 (running on one of 4 Ubuntu 20.04 VMs behind Apache 
running on the host also Ubuntu 20.04)  and I found the Select All 
check box does not check all the boxes beneath it on the Stores form. 
(If that is what you mean)






___
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] Pregeneralized DataStore and Vector-tyle

[carlo cancellieri]

Dear list,
 we're trying to configure a pregeneralized datastore to speedup the vector
tyles cache generation with no luck.

Actually asking in layerpreview for a simple application/openlayer
everything works very well.
---
14 May 20:45:36 DEBUG [renderer.lite] - Computed scale denominator:
2.7922819993363017E8
14 May 20:45:36 DEBUG [renderer.lite] - creating rules for scale
denominator - 279,228,199.934
14 May 20:45:36 DEBUG [data.util] - CRSConverterFactory can be applied from
Strings to CRS  only.
14 May 20:45:36 DEBUG [data.util] - InterpolationConverterFactory can be
applied from Strings to Interpolation only.
14 May 20:45:36 DEBUG [renderer.lite] - Processing 1 stylers for
n50:gadm36_0_3857_gen
14 May 20:45:36 DEBUG [renderer.lite] - Expanding rendering area by 2
pixels to consider stroke width
14 May 20:45:36 WARN [operation.projection] - Possible use of "Popular
Visualisation Pseudo Mercator" projection outside its valid area.
Longitude 2147483287░00.0'W is out of range (▒180░).
14 May 20:45:36 DEBUG [renderer.lite] - Querying layer
n50:gadm36_0_3857_gen with bbox: ReferencedEnvelope[-2.4862478922090434E7 :
2.4862478922090434E7, -3.604277604743299E7 : 2.4315191650220517E7]
14 May 20:45:36 TRACE [util.factory] - ENTRY  (GeometryFactory,
JTS_GEOMETRY_FACTORY)
14 May 20:45:36 TRACE [util.factory] - RETURN (GeometryFactory,
JTS_GEOMETRY_FACTORY): found implementation Optional.
14 May 20:45:36 DEBUG [data.gen] - Hint geometry distance: 62547.11678513289
14 May 20:45:36 DEBUG [data.gen] - Hint geometry distance: 62547.11678513289
14 May 20:45:36 INFO [data.gen] - Using generalizsation: postgis_n50
gadm36_0_3857 geom500 500.0
14 May 20:45:36 DEBUG [geotools.jdbc] - CREATE CONNECTION
14 May 20:45:36 DEBUG [data.jdbc] - exporting PropertyName
14 May 20:45:36 DEBUG [data.util] - CRSConverterFactory can be applied from
Strings to CRS  only.
14 May 20:45:36 DEBUG [data.util] - InterpolationConverterFactory can be
applied from Strings to Interpolation only.
14 May 20:45:36 DEBUG [geotools.jdbc] - SELECT "gid",ST_AsBinary("geom500")
as "geom500" FROM "public"."gadm36_0_3857" WHERE "geom" &&
ST_GeomFromWKB(?, 3857)
14 May 20:45:36 DEBUG [geotools.jdbc] - 1 = POLYGON ((-24862478.922090434
-19971868.88040857, 24862478.922090434 -19971868.88040857,
24862478.922090434 19971868.880408563, -24862478.922090434
19971868.880408563, -24862478.922090434 -19971868.88040857))
14 May 20:45:48 DEBUG [geotools.jdbc] - CLOSE CONNECTION
-

Once we try to ask for a mapbox vector tile (or geoJson) to WMS using the
layerpreview page, seems that the hint for the geometry distance is not
used as well.


14 May 20:49:34 DEBUG [geoserver.wms] - setting up map
14 May 20:49:34 DEBUG [data.gen] - Hint for geometry simplification in
query, fallback to base feature
14 May 20:49:34 DEBUG [data.gen] - No hint for geometry distance in query,
fallback to base feature
14 May 20:49:34 DEBUG [data.gen] - Hint for geometry simplification in
query, fallback to base feature
14 May 20:49:34 DEBUG [data.gen] - No hint for geometry distance in query,
fallback to base feature
14 May 20:49:34 DEBUG [geotools.jdbc] - CREATE CONNECTION
14 May 20:49:34 DEBUG [data.jdbc] - exporting PropertyName
14 May 20:49:34 DEBUG [data.util] - CRSConverterFactory can be applied from
Strings to CRS  only.
14 May 20:49:34 DEBUG [data.util] - InterpolationConverterFactory can be
applied from Strings to Interpolation only.
14 May 20:49:34 DEBUG [geotools.jdbc] - SELECT
"gid","gid_0","name_0",ST_AsBinary("geom") as "geom","fid" FROM
"public"."gadm36_0_3857" WHERE "geom" && ST_GeomFromWKB(?, 3857)
14 May 20:49:34 DEBUG [geotools.jdbc] - 1 = POLYGON ((-20100916.899652816
-30304381.79087722, 20100916.899652816 -30304381.79087722,
20100916.899652816 18516704.85076622, -20100916.899652816
18516704.85076622, -20100916.899652816 -30304381.79087722))
14 May 20:52:01 DEBUG [geotools.jdbc] - CLOSE CONNECTION4
--

Is this behaviour related to this thread?:
https://subscription.packtpub.com/book/application_development/9781783289615/1/ch01lvl1sec18/improving-performance-with-pregeneralized-features


If so, which is the best way to sort it out (use pregeneralized to speedup
the vector tyle generation)?

Our table has 4 geometry columns for each feature, may we can try to select
them using an appropriate style?

Thank you for your hints!

C.

-- 
Mr. Carlo Cancellieri
*skype*: ccancellieri
*Twitter*: @cancellieric
*LinkedIn*: http://it.linkedin.com/in/ccancellieri/
___
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: 

[Geoserver-users] JDBCConfig and LayerGroups

[Stefan Overkamp]

Hi list,

I'm currently testing jdbconfig (and jdbcstore) as part of having a
multiple geoserver cluster.

Importing the catalog runs fine for all object types except for
org.geoserver.catalog.LayerGroupInfo.
Only 3 to 4 from 27 LayerGroupInfo are imported.

The last LayerGroupInfo logs "Storing properties of
LayerGroupInfoImpl... with pk 832" but this pk can not found in the
object table.

Restarting Geoserver fails, when other configuration like gwc-layers
references LayerGroups which have not been imported.
Removing these references prior to import allows starting geoserver
(with the missing layergroups).

Adding layergroups afterwards is possible.
Adding layergroups to layergroups is not possible. The selection list is
empty.

Has anyone successfully imported layergroups with jdbcConfig?

Thanks

Stefan

-- 
Dipl. Ing. Stefan Overkamp
Laakmannsbusch 44, 42555 Velbert 
tel.: 0177 / 79 76 159
overk...@posteo.de



___
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 jdbcconfig

[Niels Charlier via Geoserver-users]

Hello Stefan,

Please send all your geoserver questions to the entire geoserver-users 
list, so everyone can read and respond. You can CC me if you want to 
make sure it is brought to my attention.


jdbcconfig is a community module, that means it is not 'officially' 
supported and still considered experimental. You use it at your own risk.


That said, that doesn't mean it cannot be used in production. But if you 
do, you are responsible for your own support. In fact, I use it in a 
production environment.


The import function should 'normally' import everything. It is a known 
issue of jdbcconfig that when it does fail somewhere during import, it 
just stops in the middle and does not provide any helpful logging to 
users about what went wrong 
(https://osgeo-org.atlassian.net/browse/GEOS-9532). Usually they are 
reference issues, meaning that the problem lies with inconsistencies in 
your data directory that need to be fixed in your data directory. I 
don't know what went wrong in your particular case, of course it is not 
ideal that you need to debug geoserver to find the fault in your data 
directory. Hopefully that can be fixed at some point.


You are of course welcome to make an issue on the geoserver jira and 
provide as much info as possible (check any logging).


Kind Regards

Niels

On 14/05/2020 11:48, Stefan Overkamp wrote:

Hi Niels,

I'm currently testing jdbconfig (and jdbcstore) as part of having a
multiple geoserver cluster.
Importing the catalog runs fine for:

2;org.geoserver.catalog.WorkspaceInfo;28
3;org.geoserver.catalog.NamespaceInfo;28
4;org.geoserver.catalog.DataStoreInfo;31
5;org.geoserver.catalog.CoverageStoreInfo;8
9;org.geoserver.catalog.FeatureTypeInfo;220
10;org.geoserver.catalog.CoverageInfo;8
15;org.geoserver.catalog.LayerInfo;228
18;org.geoserver.catalog.StyleInfo;160

But org.geoserver.catalog.LayerGroupInfo imports only 5 from 27 LayerGroups.

Is jdbcconfig production ready?

Greetings

Stefan




___
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] GeoS 2.17.0 problem removing layers

[Russ Hore]

I have GS2.17.0 (running on one of 4 Ubuntu 20.04 VMs behind Apache running on 
the host also Ubuntu 20.04)  and I found the Select All check box does not 
check all the boxes beneath it on the Stores form. (If that is what you mean)

Ubuntu: 11.0.7 (OpenJDK 64-Bit Server VM)
Tomcat 9

I also check the Layers, Layer Groups and Workspaces and it is the same. It is 
not a problem for me as I only have a few layers but happy to test anything if 
people tell me what needs testing?

Looking at the Workspaces source code for the Select All check box it has;






Workspace Name

and father up;
Wicket.Ajax.ajax({"u":"./org.geoserver.web.data.workspace.WorkspacePage?17-2.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll=false","m":"POST","c":"idd9","i":"ajaxFeedback","e":"click"});;



Russ

> On 14 May 2020, at 00:45, Tom S  wrote:
> 
> Things work as expected under an older system with Tomcat 8 and JRE 1.8.
> 
> Also, while reviewing and doing the 'GeoServer cleanup' task (remove jai* 
> jars) found on 
> https://docs.geoserver.org/stable/en/user/production/java.html#production-java
> 
> for 1.17.0, the program will no longer run properly (in the new environment).
> 
> 
> On 5/13/2020 4:15 PM, Tom S wrote:
>> I will double check that, but the problem exists even with the default data 
>> set.  I also see the same issue under Chrome and with GeoS V1.16.2.  The 
>> test system I am using has the latest tomcat 9.x and AdoptOpenJDK 11.x - I 
>> might try it on a different system with JDK 8.
>> 
> 
> 
> ___
> 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 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] Can't find a response parser factory for DESCRIBE_FEATURETYPE/'application/octet-stream'

[Ron Lindhoudt via Geoserver-users]

 You are right, the content-type of the WFS was not corrected.It is corrected 
now.
On Monday, 11 May 2020, 21:46:57 CEST, mark  wrote:  
 
  I think geoserver is complaining about the response mime type, 
'application/octet-stream' is not understood (also looking at the capabilities 
it is not listed as a response type for any of the operations (so it is 
invalid)  
  hth, Mark 
   ( I may be wrong)
  
  On 2020-05-11 14:01, Ron Lindhoudt via Geoserver-users wrote:
  
 
 Hi Ian, 
  I tried the same with the latest version 2.17.0 of Geoserver and the error is 
the same for WFS 
https://geodata.gwsw.nl/Buren/Netwerk?service=WFS=GetCapabilities
  
  
   org.apache.wicket.WicketRuntimeException: Method onRequest of interface 
org.apache.wicket.behavior.IBehaviorListener targeted at 
org.apache.wicket.ajax.markup.html.AjaxLink$1@61bca0a4 on component [AjaxLink 
[Component id = link]] threw an exception at 
org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268)
 at 
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
 at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:248)
 at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:234)
 at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895)
 at 
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
 at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265) 
at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222)
 at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
 at 
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:261)
 at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:203)
 at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at 
org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:166)
 at 
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
 at 
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:52)
 at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040)
 at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943)
 at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
 at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623)
 at 
org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:26)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
 at 
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:69)
 at org.geoserver.wms.animate.AnimatorFilter.doFilter(AnimatorFilter.java:70) 
at 
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:66)
 at 
org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:41)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
 at 
org.geoserver.platform.AdvancedDispatchFilter.doFilter(AdvancedDispatchFilter.java:37)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
 at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:320)
 at 
org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:70)
 at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
 at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
 at 
org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:74)
 at 
org.geoserver.security.filter.GeoServerCompositeFilter.doFilter(GeoServerCompositeFilter.java:91)
 at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334)
 at