Deploying the GDAL ImageI/O-Ext native libraries in a location referred by the PATH environment variable (like, as an instance, your JDK/bin folder) allows GeoServer to successfully recognize them when invoked via the start.bat script. However, this does not seem to work when running GeoServer as a service on Windows. As a result, during the service startup, GeoServer log reports this worrysome message:
it.geosolutions.imageio.gdalframework.GDALUtilities loadGDAL
WARNING: Native library load failed.java.lang.UnsatisfiedLinkError: no gdaljni in java.library.path
Taking a look at the wrapper.conf configuration file available inside the GeoServer installation (at bin/wrapper/wrapper.conf), we can find this useful entry:
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=bin/wrapper/lib
To solve the issue, you have 2 possible ways:
- move the native DLLs on the referred path (bin/wrapper/lib)
- add a wrapper.java.library.path.2=path/where/you/deployed/nativelibs entry just after the wrapper.java.library.path1=bin/wrapper/lib line.
![GDAL plugins available](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7BH-zr7Y5aLbCyme_nixlmCjO-UF0B1RWZ3hYnZ7J3BxiwpE1H2P1rYBiXYzg9jEzQJfSYsrmiEDYI2hgX-7Bzn08RPuvn0oAcdFaMq7uF6sSCkR5bWJIkkX-pJX6PnMm0_iAstf9Z9Q/s320/GDALFormats.png)
Tidak ada komentar:
Posting Komentar