[Geoserver-users] GetFeature proxy redirection

[Nicolas De Ville de Goyet]

Hello everyone,

I'm struggling with GetFeature requests to geoserver behind a proxy.

I followed the instructions here and modified the web.xml document to 
allow the redirection:


/https://docs.geoserver.org/latest/en/user/security/webadmin/csrf.html/

My problem is that the proxy translates the 'special' characters in 
hexadecimal form in the GetFeature request (i.e.: workspace:feature --> 
workspace%3Afeature) and geoserver is not able to understand the request.


Any advice how to configure geoserver or the proxy to solve the issue?

Many thanks/
/

--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
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] GetFeature proxy redirection

[Nicolas De Ville de Goyet]

Hello Andrea,

Thanks for your reply.

The error arise when I'm in the Layer preview page on geoserver itself. 
The url is this one: https://spatial.naturalsciences.be/geoserver/web/


To reproduce the error, search the layer borehole. Then download the gml 
preview (max 50 features):


http://spatial.naturalsciences.be/geoserver/ge/ows?service=WFS=1.0.0=GetFeature=*ge%3Aborehole*=50

--> error message: locator="typeName"> Feature type :ge%3Aborehole unknown 


Then correcting the url:

http://spatial.naturalsciences.be/geoserver/ge/ows?service=WFS=1.0.0=GetFeature=*ge:borehole*=50

I get the output I need.

So I'm a bit confuse at where I should fix the problem... I'm 
downloading directly on geoserver so it should understand the URL encoding?!


Any advice?

Thanks a lot,

Nicolas

On 05/10/2020 12:55, Andrea Aime wrote:
On Mon, Oct 5, 2020 at 12:31 PM Nicolas De Ville de Goyet 
mailto:ndevi...@naturalsciences.be>> wrote:


My problem is that the proxy translates the 'special' characters
in hexadecimal form in the GetFeature request (i.e.:
workspace:feature --> workspace%3Afeature) and geoserver is not
able to understand the request.

That looks like URL encoding, GeoServer is able to recognize it as 
long as the request is a GET request.
If the request is a POST XML and the contents of the XML have been URL 
encoded, then well, it won't of course.


An example of URL encoded that just works with an online GeoServer:
https://tb16.geo-solutions.it/geoserver/oszoom/ows?service=WFS=1.0.0=GetFeature=oszoom%3Aairports=50

By the way, the URL encoding is not really handled by GeoServer, it's 
the web container running GeoServer that handles it, e.g., Jetty, or 
Tomcat, or whatever is used in your installation.

GeoServer receives the request already decoded.

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 
--- /Con 
riferimento alla normativa sul trattamento dei dati personali (Reg. UE 
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si 
precisa che ogni circostanza inerente alla presente email (il suo 
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è 
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il 
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra 
operazione è illecita. Le sarei comunque grato se potesse darmene 
notizia. This email is intended only for the person or entity to which 
it is addressed and may contain information that is privileged, 
confidential or otherwise protected from disclosure. We remind that - 
as provided by European Regulation 2016/679 “GDPR” - copying, 
dissemination or use of this e-mail or the information herein by 
anyone other than the intended recipient is prohibited. If you have 
received this email by mistake, please notify us immediately by 
telephone or e-mail./



--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
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] App-schema gml namespace

[Nicolas De Ville de Goyet]

Hello everyone,

I'm using geoserver 2.13.1 with an App-schema DataAccess uploaded with 
Hale studio software.


When I download a gml in geoserver, by default, it includes at the 
beginning of the gml file the namespace of all the workspaces present in 
my geoserver. I tried to isolate the workspace to avoid that but It 
doesn't change anything. To simplify the gml document I wish to remove 
the extra-namespaces.


I'm not sure it is related to that but the gml file do not pass the 
Inspire validator test. The error message is:


/XML document 'test.gml': 
http://ears.bmdc.be:80/geoserver/schemas/wfs/2.0/wfs.xsd, 2:35: 
s4s-elt-character: Non-whitespace characters are not allowed in schema 
elements other than 'xs:appinfo' and 'xs:documentation'. Saw '301 Moved 
Permanently'./


It looks like the error is in the wfs.xsd schema, which is a file I'm 
not supposed to change I guess. Maybe the problem is linked to 
namespaces declaration at the beginning of the gml document?!


Any advice are most welcome!

Best,

--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
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] Password-protected WMS

[Nicolas De Ville de Goyet]

Dear all,

I'm trying to find out if it is possible to use an WMS with a password 
so only chosen users can access the layers on it.


In geoserver, I have one workspace (among others) which shall not be 
public. Its uses is only for internal colleagues who do not know much 
about geoserver and web-services; My goal would be to provide them a WMS 
link to the specific workspace they can add as a service in the 
Geonetwork map viewer.


I tried:

MYSERVER.be/geoserver/MYWORKSPACE/wms?service=WMS=1.1.0=myusername=mypassword

It seems there are at least two problems. The WMS getcapabilities does 
not seems to accept limitation to a specific workspace and the 
user/password is not recognized.
I understand the security of such method is quite limited (password 
written in clear) but given my context it is acceptable.


Does anyone knows if this is possible to do and how to do it?
Many thanks,


--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
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] Password-protected WMS

[Nicolas De Ville de Goyet]

Many thanks for your replies. This gives good food for thought.

Have a nice day,

Nicolas de Ville

On 18/05/2021 00:45, Humphries, Graham wrote:


We have set up Geoserver such that when an external request comes in, 
a basic authentication code is added to the request header by the web 
server. Similarly if the request is from an internal source a 
different basic authentication code as added to the request header.


This allows internal users to have access to different layers than 
external users without requiring the operator to add usernames and 
passwords to the request.


This has been working well for us where we only need to differentiate 
between internal and external users.


Hope this helps

Regards,

Graham H

*From:*Nicolas De Ville de Goyet [mailto:ndevi...@naturalsciences.be]
*Sent:* Monday, 17 May 2021 8:54 PM
*To:* GeoServer Mailing List List 
*Subject:* [Geoserver-users] Password-protected WMS

Dear all,

I'm trying to find out if it is possible to use an WMS with a password 
so only chosen users can access the layers on it.


In geoserver, I have one workspace (among others) which shall not be 
public. Its uses is only for internal colleagues who do not know much 
about geoserver and web-services; My goal would be to provide them a 
WMS link to the specific workspace they can add as a service in the 
Geonetwork map viewer.


I tried:

MYSERVER.be/geoserver/MYWORKSPACE/wms?service=WMS=1.1.0=myusername=mypassword

It seems there are at least two problems. The WMS getcapabilities does 
not seems to accept limitation to a specific workspace and the 
user/password is not recognized.
I understand the security of such method is quite limited (password 
written in clear) but given my context it is acceptable.


Does anyone knows if this is possible to do and how to do it?

Many thanks,

--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be  
<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.bmdc.be%2F=04%7C01%7Cndeville%40naturalsciences.be%7Cff68283ec9ec408b283308d919858e04%7C4da8d35db472419c9e15665786aadbfb%7C0%7C0%7C637568884239064429%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=YTOvaci28lHyzwHeFk71fCMTj%2Ftb8r0masTFFUAjU9Y%3D=0>
https://metadata.naturalsciences.be/  
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmetadata.naturalsciences.be%2F=04%7C01%7Cndeville%40naturalsciences.be%7Cff68283ec9ec408b283308d919858e04%7C4da8d35db472419c9e15665786aadbfb%7C0%7C0%7C637568884239064429%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=L9p9u5un38Zj%2B0DAq4lnzr1BR%2BrPzbYJT47MYaECh90%3D=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.


--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
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 upgrade - login fail

[Nicolas De Ville de Goyet]

Dear all,

I just upgraded my geoserver instance from 2.13 to 2.19.2 and I can't 
login anymore. The error message is :


 * Invalid username/password combination.

Nothing comes out in the logs.

I transferred the data directory to the new geoserver and all my layers 
can be previewed. If I check the file 
./geoserver/data/security/usergroup/default/users.xml I can still see 
all the registered users.


What am I missing? Are there an additional steps to perform for a 
successful update?


Thanks for your help.

Best regards,

--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
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] http error 400 - bad request

[Nicolas De Ville de Goyet]

Dear all,

I'm running geoserver 2.18.5 on tomcat and I can't make it work properly.

I can login as admin or any other registered user, but I can't navigate 
inside the geoserver GUI. If I try to save any modification (on 
workspace, layer, settings, ...) I receive a 400 error.


A similar issue has been discussed in the link below but without the 
ability to save any change I can't test the suggested solution:


https://stackoverflow.com/questions/66526411/geoserver-advice-please-http-status-400-bad-request

My (test) geoserver instance is available here: 
https://ears.bmdc.be/geoserver/


You'll see that it is not possible to navigate in the preview layer. I 
have the same error with geoserver 2.19.2.


I don't get any error message in the log.

Any suggestion?

Many thanks,

--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/



___
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 upgrade - login fail

[Nicolas De Ville de Goyet]

Dear all,

Thank you for your replies.

Downgrading to version 2.18.5 seems to solve the password issue. I'll 
try your solution of admin password reset with newer version.


Best regards ,

Nicolas de Ville

On 15/10/2021 13:39, Mark Prins wrote:


If I check the file
./geoserver/data/security/usergroup/default/users.xml I can
still see all the registered users.

If all else fails you can reset the admin password in that file to 
plain text and then update all (including admin) passwords from the 
GUI (that should then use the new encryption algo).
see eg. 
https://geoserver-users.narkive.com/rDV1AUhb/forgot-the-geoserver-login-password#post2 



--
Disclaimer;
This message is just a reflection of what I thought at the time of 
sending. The message may contain information that is not intended for 
you or that you don't understand.



___
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


--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
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] http error 400 - bad request

[Nicolas De Ville de Goyet]

Dear,

For the record, I solved my issue with the correct definition of of the 
CSRF white list parameter in the web.xml file.
It was enable but with an error in it and the log doesn't give clues 
about it.


Hope this help!

Cheers,

Nicolas de Ville

On 19/10/2021 11:24, Nicolas De Ville de Goyet wrote:

Dear all,

I'm running geoserver 2.18.5 on tomcat and I can't make it work properly.

I can login as admin or any other registered user, but I can't 
navigate inside the geoserver GUI. If I try to save any modification 
(on workspace, layer, settings, ...) I receive a 400 error.


A similar issue has been discussed in the link below but without the 
ability to save any change I can't test the suggested solution:


https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F66526411%2Fgeoserver-advice-please-http-status-400-bad-requestdata=04%7C01%7Cndeville%40naturalsciences.be%7C705f4c9e26b54c1d208508d992f8ad89%7C4da8d35db472419c9e15665786aadbfb%7C0%7C0%7C637702419584449021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=VynPA7h7RPkXHS0tSxwg1GFqhZHDMV%2Bi5WE6FRixJjY%3Dreserved=0 



My (test) geoserver instance is available here: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fears.bmdc.be%2Fgeoserver%2Fdata=04%7C01%7Cndeville%40naturalsciences.be%7C705f4c9e26b54c1d208508d992f8ad89%7C4da8d35db472419c9e15665786aadbfb%7C0%7C0%7C637702419584449021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=jKh4Bm0irvkTp0pkm4ZDTNauqwk2rh4R0jxPQdbwERs%3Dreserved=0


You'll see that it is not possible to navigate in the preview layer. I 
have the same error with geoserver 2.19.2.


I don't get any error message in the log.

Any suggestion?

Many thanks,


--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/



___
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] Save Cascade WMS layers locally

[Nicolas De Ville De Goyet]

Hello everyone,

The context:

I have a running geoserver (https://spatial.naturalsciences.be) that 
works fine. This is my main Geoserver instance. The layers are a 
combination of several different data stores (GIS layers, PosgreSQL 
database,...).


I have another geoserver instance running on a research vessel. This 
vessel has poor (and expensive) connectivity when cruising.


I would like to visualize the layers from the main geoserver on-board 
even if there is no internet connection.


My question is:

    - Is it possible to populate the on-board geoserver by saving 
locally the layers available via the main WMS?


I see there is some documentation on cascading WMS but it needs to 
remain connected to the source.


Many thanks for your help/ideas,

Nicolas de Ville



___
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] Failing Postgis store when upgrading geoserver to 2.22.1

[Nicolas De Ville De Goyet]

Dear,

I upgraded my geoserver instance to 2.22.1 and it created issues with 
all my postgis stores.


https://spatial.naturalsciences.be/

The previous version I had is 2.19.2

Now, when I try to connect/download my layers I get the following error 
message:


version="1.1.1" >   
  java.lang.reflect.UndeclaredThrowableExceptionUnable to obtain 
connection: Cannot create PoolableConnectionFactory (Something unusual 
has occurred to cause the driver to fail. Please report this exception.)
Cannot create PoolableConnectionFactory (Something unusual has occurred 
to cause the driver to fail. Please report this exception.)
Something unusual has occurred to cause the driver to fail. Please 
report this exception.

class org.postgis.PGbox2d

The other type of data (GeoTiff, shapefiles, ...) are working as expected.

Do you have an idea on the reason of such an issue?

Many thanks for your help,

Nicolas de Ville



___
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] Failing Postgis store when upgrading geoserver to 2.22.1

[Nicolas De Ville De Goyet]

Dear Jody and Hans,


Thanks a lot for your answers.


You nailed it properly both of you. There was a conflict between two 
postgres jdbc drivers.


One was under tomcat/lib and a new one was added under 
tomcat/webapps/geoserver/WEB-INF/lib when I made the upgrade.



Again thank you for your help, it would have taken me ages to find that...


Have a good evening,


Nicolas


On 7/02/23 19:20, Hans Yperman wrote:

I see a few ways forward:

 1. in the geoserver logs , you should be able to find the complete
stack trace, of which this is only a part. Can you paste that here?
 2. There is a suspicious class org.postgis.PGbox2d in there.  Maybe
the postgres server has also been upgraded, and the postgis
extension is missing?
 3. You have some kind of class loader conflict, e.g. 2 different
postgres jdbc drivers.  For tomcat: Can you tell which files
postgresql*.*  exist under tomcat/lib and under
tomcat/webapps/geoserver/WEB-INF/lib  .  There should be only 1.



*Hans Yperman*

Department IT





*Vlaams Instituut voor de Zee vzw*

InnovOcean Campus, Jacobsenstraat 1

8400 Oostende, België

☎+32 (0) 59 33 61 13

hans.yper...@vliz.be

*www.vliz.be 
<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vliz.be%2F=05%7C01%7Cndeville%40naturalsciences.be%7Cecbf64684eba4599040608db09380764%7C4da8d35db472419c9e15665786aadbfb%7C1%7C0%7C638113908498099523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rg18OBiDpiI%2Fgn%2BewtrJDFrEvHp6CF82SGafkoMalls%3D=0>***



*Van:* Nicolas De Ville De Goyet 
*Verzonden:* dinsdag 7 februari 2023 15:09
*Aan:* GeoServer Mailing List List 
*Onderwerp:* [Geoserver-users] Failing Postgis store when upgrading 
geoserver to 2.22.1

Dear,

I upgraded my geoserver instance to 2.22.1 and it created issues with
all my postgis stores.

https://spatial.naturalsciences.be/

The previous version I had is 2.19.2

Now, when I try to connect/download my layers I get the following error
message:

version="1.1.1" >   
java.lang.reflect.UndeclaredThrowableExceptionUnable to obtain
connection: Cannot create PoolableConnectionFactory (Something unusual
has occurred to cause the driver to fail. Please report this exception.)
Cannot create PoolableConnectionFactory (Something unusual has occurred
to cause the driver to fail. Please report this exception.)
Something unusual has occurred to cause the driver to fail. Please
report this exception.
class org.postgis.PGbox2d

The other type of data (GeoTiff, shapefiles, ...) are working as expected.

Do you have an idea on the reason of such an issue?

Many thanks for your help,

Nicolas de Ville



___
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#/ 
<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ianturton.com%2Ftalks%2Ffoss4g.html%23%2F=05%7C01%7Cndeville%40naturalsciences.be%7Cecbf64684eba4599040608db09380764%7C4da8d35db472419c9e15665786aadbfb%7C1%7C0%7C638113908498099523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=bsiGoPGkrMNBPuFN2c1ZmXv8ZnDcj2opCnPVol658Jw%3D=0>
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html 
<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgeoserver.org%2Fcomm%2Fuserlist-guidelines.html=05%7C01%7Cndeville%40naturalsciences.be%7Cecbf64684eba4599040608db09380764%7C4da8d35db472419c9e15665786aadbfb%7C1%7C0%7C638113908498099523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=SkcFthcOCI7zcOUmslTbM2LObcIWsi8ve2%2BBoGdAeSA%3D=0>


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 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgeoserver%2Fgeoserver%2Fwiki%2FSuccessfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer=05%7C01%7Cndeville%40naturalsciences.be%7Cecbf64684eba4599040608db09380764%7C4da8d35db472419c9e15665786aadbfb%7C1%7C0%7C638113908498099523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=kFtKmv4Aipw3uKQUhgv82DEmmPRWoaEgERt8tfoxMOM%3D=0>



Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users 
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fgeoserver-users=05%7C01%7Cndeville%40naturalsciences.be%7Cecbf64684eba4599040608db093