Caused by: org.opengis.referencing.NoSuchAuthorityCodeException: No code “EPSG:4326” from authority “European Petroleum Survey Group” found for object of type “IdentifiedObject”.
at org.geotools.referencing.factory.AbstractAuthorityFactory.noSuchAuthorityCode(AbstractAuthorityFactory.java:908)
We are using java 1.8, wildlfy 11. Anything related with Memory (buffer/cache)
Please advice on this for a solution
Well since 2.22.x Java 8 is not supported (https://docs.geoserver.org/latest/en/user/production/java.html#use-supported-jre) and the reccommeed version of wildfly is 14 (with setup changes) see https://docs.geoserver.org/latest/en/user/production/java.html#running-on-java-11 for more details.
Ian
Hi,
That’s strange. Can you provide exact steps to reproduce the issue?
- GeoServer version
- Deployment method
- How/when does this error occur?
Do you have a file named gt-epsg-hsql-XXX.jar in WEB-INF/lib/, where XXX stands for the version number?
Hi,
your setup is problematic:
- The GeoServer 2.20.x has been out of support for almost three years now
- GeoServer 2.20.4 has 15 known CVEs, one of which is an unathenticated remote code execution exploited in the wild.
- GeoServer is tested against Jetty and Tomcat, not Wildfly
Warm reccomendation: update to GeoServer 2.26.2, Java 11 and Tomcat 9 at the earliest convenience. Who knows, the EPSG problem might also disappear while you perform these steps.
I understand this is a large change. Commercial support providers are available, they might help you with the upgrade. Some might even provide a fully patched 2.20.4, if you sponsor the developer time needed to fix all of the CVEs known in 2.20.4 (to be analyzed, some backports might be too hard).
Cheers
Andrea
What request triggers that error? The same error message appears here New GeoServer WFS error NoSuchAuthorityCodeException - Geographic Information Systems Stack Exchange.
-Jukka Rahkonen-
Usually it is a permission or sandboxing issue. Trouble unpacking epsg database in order to lookup the code.
Previous guidance for different app servers each had their own procedure to follow.
yes we do have the gt-epsg-hsql-26.4.jar file in the said folder. The jar file is already in the package when downloaded.
@tanishcb I am not sure if you saw above, you are working on an outdated version, in an environment that is not tested and supported by the community.
-
The availability of the jar is not the issue, the ability of geoserver to write out the database is.
-
The GeoTools code is here if you wish to review HsqlEpsgDatabase.java . You can see it taking steps to use
java.io.tmp
location, and create aGeoTools/Database/HSQL
folder to unpack the database into. -
The specifics of how
java.tmp.dir
is managed, and if GeoServer has access to create files and folders, is different for each Application Server and you can read a bit about wildfly.
It should be possible to get GeoServer working with some effort (it has worked in the past). If you can provide instructions or application changes we would welcome your experience - we can only support environments that people such as yourself can provide instructions and testing for.
ok, exactly it was the permission issue for the geoserver.war file in the temp folder of wildfly
/app/wildfly-11.0.0.Final/standalone/tmp
Write Permission for wildfly user has to be given for the owner
Octal:0777
Check the box : set owner, group and permission recursively
Oh nice you got it working!
Can you make some instructions for the docs? It would be nice for the next wildfly user to have less trouble
I would be also kind of you test 2.27.0 on WildFly when we ask for help in next month.