Try searching your Tomcat directory for a xercesImpl jar file and removing it
if it's there. Do you have either the Printing or GeoFence Server extensions
installed? I did a quick grep search and those are the only two modules that
explicitly include xercesImpl.
Steve Ikeoka
There are problems with GeoServer's Hazelcast modules in versions 2.24.0 and
2.24.1 caused by attempting to upgrade the Hazelcast library. You can either
downgrade to 2.23.4 which uses an older Hazelcast version or wait until 2.24.2
is released in a couple of weeks. There will be changes to
This is possibly a regression from the fix for this issue:
https://osgeo-org.atlassian.net/browse/GEOS-10903
Steve Ikeoka
From: Rahkonen Jukka
Sent: Friday, November 10, 2023 12:34 AM
To: Jody Garnett ; Aaron Sedgmen
Cc: geoserver-users@lists.sourceforge.net
This is a regression from the following commit that got missed because the bug
wasn't covered by existing unit tests:
https://github.com/geoserver/geoserver/commit/587768dfcbe166bbf7972d172f454f1b3f17a043#diff-cb964c0310e4da804603b89cac17d51824cc66e2f626c4af6902610c8a8e9329
Getting rid of the
I was upgrading from GeoServer 2.22.4 to 2.22.5 using the Web Archive (WAR)
package and deploying in JDK8 and encountered a NoSuchMethodError related to
compiling the GeoTools JARs with JDK11. I was able to reproduce the error
using the unmodified WAR directly from the download site and the
I looked at the example URL and it is getting blocked because of a
"java.net.URISyntaxException: Illegal character in query". The URL checking
feature was modified to reject URLs that contain invalid characters to prevent
them from bypassing the URL normalization and allowing access to
I haven't tested it through the REST API but there are separate default
interpolation method settings for WCS and WMS.
The WCS setting is in the coverage.xml and is one of "nearest neighbor",
"bilinear" and "bicubic":
bicubic
The WMS setting is in the layer.xml and is one of "Nearest",
